-
Notifications
You must be signed in to change notification settings - Fork 11
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
Automatize submodule PR if framework name matches with submodules #250
Automatize submodule PR if framework name matches with submodules #250
Comments
I need to create a personal access token to be capable to perform the PR in a different repo inside rest-for-physics. And I would prefer not to use my personal access token. Do you think is a good idea to create a rest-for-physics account (mail) from which we can create the personal access token? @jgalan and @lobis let me know what do you think. |
Yes, I believe we already have one email account for rest-for-physics at google. I let you know via slack. |
Thanks, a personal access token has been created with this account and have been added to secrets. Note that this account has been added to the owners of the github rest-for-physics repo. |
Now has been downgraded to member with some privileges since ownership was not needed. However, if you want to centralize ownership for rest-for-physics we can set this account as owner. |
If you go to https://analytics.google.com using that account you may check the user activity at https://sultan.unizar.es/rest/ and at https://rest-for-physics.github.io |
This year activity at https://rest-for-physics.gihub.io since January |
April is the publication @nkx111 |
Recently we faced some issues when a submodule PR is merged while the required PR in
framework
is not merged. This issue can be addressed by automatizing the PR inframework
when a branch of the same name is present in any submodule. This in principle can be done with adependantbot
https://docs.github.com/en/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions. We need the following requirements:framework
should trigger any submodule PR with a matching branch name.framework
the different submodule PR should be also merged.framework
framework
branch should not be allowed.The text was updated successfully, but these errors were encountered: