5f6018c6cd
Turns out they're not actually needed, because the implementation of "finding all commits" just iterates over the lines of the `git log` output, anyway - no need to actually traverse the tree. I am _reasonably_ sure this means that it's no longer a pre-requisite that the source repo has linear history, either. If I discover during adding tests that that actually is the case, I'll re-add that note.
13 lines
739 B
Plaintext
13 lines
739 B
Plaintext
- [ ] Make example of templatized workflow, that uses `github` context variables to fetch source repository owner and
|
|
name, and that fetches secret from Vault
|
|
- [ ] Add a link to the original commit from the body of the file that's created in the target repo, and/or in the
|
|
commit body.
|
|
- [ ] Allow passing a `limit` variable to control how many source commits to read
|
|
- [ ] allow passing 0 to indicate all
|
|
- [ ] Flesh out the `README.md` just before pushing with a description of what this tool is
|
|
- Doing it just before push, rather than on first creation, so that it will be added even to target repositories that
|
|
have already been initialized with this tool
|
|
- [ ] Blog about this ;)
|
|
- [ ] Tests!
|
|
- [ ] ...
|
|
- [ ] Profit? |