Philip Holleran
Philip Holleran
@bkeepers - while I agree that would be nice, I am đ with a workflow where the inheriting repo checks for and applies the latest permissions upon the next push....
@bkeepers - would it be reasonable, then, to not ignore all other pushes? Would this be lighter touch than trying to propagate changes down to the inheriting repos?
or, alternatively, would it make sense to explore a "hacky" solution with [probot/metadata](https://github.com/probot/metadata) in which we utilize a closed issue to store the last synchronized commit SHA of `myOrg/.github/settings.yml` and...
@weedz - thanks for the help. I'm getting closer. I implemented your second suggestion and am no longer getting an error. Interestingly, the push is not going through to GitHub....
@leodido - thanks for the idea, I like it. Feel free to submit a PR if you already have something worked out.
@gr2m - I'm glad to see you are finding value in my little app. I like your suggestion and would welcome your thoughts on this potential approach: * The app...
@gr2m - I noticed your `toc.yml` file is in a `.github` folder nested within another `.github` folder. Does it still function this way if the `toc.yml` file is in the...
@gr2m - Thanks for your patience and sorry for mis-reading that path âšī¸ . I looked in to your original question and was able to successfully use a centralized `toc.yml`...
Removing the stale logo as I want to keep this open and move to the new probot pattern for `.github` configuration repositories.
I and GitHub are interested in participating đ