-
Notifications
You must be signed in to change notification settings - Fork 192
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
Fix UML permissions from forks / Run only on merge to main #967
Conversation
…ng into fix-uml-permissions
Couldn't figure out the permissions as it would require the fork's owner to have the action bot permissions. Because of that, I just have it that if only runs when pymc-labs is the owner. In a fork's case, it should only run when it is merged in. Which still keeps it up to date. How does that sounds @juanitorduz ? An alternative is to only run on merge to main. Do you have a preference? |
Personally, running only on main merge might be fine so that developer doesn't have to |
The change on this PR looks good! Still, running only on main merge seems more convenient as you suggest, Feel free to push the change. |
…#967) * change repo and python file change to kick off * comment to check for failure * using the repo * delete to trigger * the previous trigger * push up again * check for the owner being pymc-labs * remove unused * only run after merge to main
* change repo and python file change to kick off * comment to check for failure * using the repo * delete to trigger * the previous trigger * push up again * check for the owner being pymc-labs * remove unused * only run after merge to main
* change repo and python file change to kick off * comment to check for failure * using the repo * delete to trigger * the previous trigger * push up again * check for the owner being pymc-labs * remove unused * only run after merge to main
Description
Related Issue
Checklist
Modules affected
Type of change
📚 Documentation preview 📚: https://pymc-marketing--967.org.readthedocs.build/en/967/