Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Template main.yml workflow to enable feedback from tooling repo #1

Closed
blakeNaccarato opened this issue Aug 14, 2021 · 1 comment
Closed
Labels
enhancement New feature or request

Comments

@blakeNaccarato
Copy link
Member

blakeNaccarato commented Aug 14, 2021

Dependabot runs over in blakeNaccarato/tooling. When a pull request is merged over there, I want the updated dependency to show up as a commit on this repo. That can be done by writing an update job into main.yml that needs all the other jobs in main.yml to succeed. Then, update will propagate changes back to blakeNaccarato/copier-python/template. This automates that section of the "loop" between the two repos.

The other end of the "loop", updating blakeNaccarato/tooling whenever the template changes, is less automatable. The questions/answers might change so the automation would be fragile. There is currently no way to not run a job if a certain file changes.

The update job shouldn't leak into my other projects, so it should be protected behind Jinja conditionals. That conditional could be tied to the gitignore_dependencies question which should probably be generalized to are_we_in_tooling or something.

Once this automation is established, it should become easier to maintain tooling, as bumped Dependencies will come as new commits.

@blakeNaccarato
Copy link
Member Author

This is no longer necessary as all updates are either automatically handled here or manually propagated from blakeNaccarato/tooling.

@blakeNaccarato blakeNaccarato added the enhancement New feature or request label Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant