We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I can't see a reason to wait on them
They've been really stable and I've never had to adjust them other than enabling CD when people ask sometimes
The main reason they stay open sometimes is someone hasn't logged into artifactory.
Now that we enforce logging in as part of hosting flow they go green straight away
Example PR: #2298
Assuming it's supported in the library we use the change needs to be around here: https://github.com/jenkins-infra/repository-permissions-updater/blob/master/src/main/java/io/jenkins/infra/repository_permissions_updater/hosting/Hoster.java#L366
No response
The text was updated successfully, but these errors were encountered:
Looks like this will do it https://github.com/peter-evans/enable-pull-request-automerge
Sorry, something went wrong.
No branches or pull requests
What feature do you want to see added?
I can't see a reason to wait on them
They've been really stable and I've never had to adjust them other than enabling CD when people ask sometimes
The main reason they stay open sometimes is someone hasn't logged into artifactory.
Now that we enforce logging in as part of hosting flow they go green straight away
Example PR:
#2298
Assuming it's supported in the library we use the change needs to be around here: https://github.com/jenkins-infra/repository-permissions-updater/blob/master/src/main/java/io/jenkins/infra/repository_permissions_updater/hosting/Hoster.java#L366
Upstream changes
No response
The text was updated successfully, but these errors were encountered: