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

Extract sync-defaults action #265

Closed
patcon opened this issue Apr 24, 2022 · 2 comments · Fixed by #266
Closed

Extract sync-defaults action #265

patcon opened this issue Apr 24, 2022 · 2 comments · Fixed by #266

Comments

@patcon
Copy link

patcon commented Apr 24, 2022

Hi there! I came across your repo via repository-settings/app#518 (comment)

I feel like your solution here is really great, but it seems that I can't actually use this GitHub Action outside the context of exivity. Is that correct?

These are my failed attempts, for what it's worth:
https://github.com/g0v-network/domains/actions/workflows/sync-repo-settings.yml

Curious to know your thoughts! Wondering if maybe (so as not to get in the way of your monorepo flow) the org owner could just be made more configurable here, as I believe that's part of the snag :)

const repo = {
owner: 'exivity',
repo: component,
}


PS, you might get a kick out of using this github action to get ephemeral tokens from a github app scoped to just your organization: https://github.com/peter-murray/workflow-application-token-action

@hongaar
Copy link
Contributor

hongaar commented Apr 25, 2022

Hi! Thanks for chiming in here. Your feedback is appreciated and you make a valid point. Currently, this repo is not ready for use outside the exivity org.

I'll make an attempt to make the actions in this repo more generic to make them more re-usable (e.g. infer the owner from the current repo owner by default, etc.).

PS, you might get a kick out of using this github action to get ephemeral tokens from a github app scoped to just your organization: https://github.com/peter-murray/workflow-application-token-action

Interesting approach, I'll try this!

@hongaar
Copy link
Contributor

hongaar commented Apr 26, 2022

@patcon I've merged a PR which addresses this. If you have a chance, you can try out these changes now. Let me know if you have any further ideas!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants