-
Notifications
You must be signed in to change notification settings - Fork 122
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
org-level commit types #87
Comments
That's correct. I know @gr2m, @IAmHughes, @RichardLitt, and @wooorm have all worked on projects to help sync repo configuration across orgs. Any tips, y'all? |
I use shell scripts to check the existence of files, as it's normally the easiest, by cloning all of the repos locally. Upload a config file to each repo, or point to a single master file in a .github repo or something similar. :) |
Is it not possible to enhance the GitHub app to accept settings? |
I started stubbing out a PoC here: https://github.com/IAmHughes/sync-action-workflow-across-org Unfortunately I haven't had time to go back to it yet after hitting a hurdle with Octokit described here: https://github.com/octokit/rest.js/issues/1656 The plan was for an action that triggers off of a push event, checks if the push contained changes to a whitelist set of workflows, then will create PRs to all the repos in your repo whitelist to update the workflow. |
Not entirely sure how I can help, but here’s a quick intro in my experience: |
Probot supports owner-wide configuration. Just create a |
That works out of the box!? |
I think so? If I recall correctly we incorporated the functionality of probot-config into probot core |
I will try this tomorrow thanks! |
Created https://github.com/graphql-nexus/.github and trying to test here https://github.com/graphql-nexus/test/pull/1 but not confident with result because even a blatantly incorrect title is showing as a PASS. 🤔 |
It looks like you have That suggests to me that the config is actually working, as |
Yeah my bad I was thinking as if the This is awesome thanks everyone! |
I would like to augment the supported semantic version types at the org level. It is currently only possible at the repo level via config file, correct?
The text was updated successfully, but these errors were encountered: