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

branchprot: Exclude buildpack repos managed by CI #832

Merged
merged 1 commit into from
May 2, 2024

Conversation

@arjun024 arjun024 marked this pull request as draft April 30, 2024 16:39
@arjun024 arjun024 force-pushed the buildpacks-ci-push-repos branch from ebb204f to 2602461 Compare April 30, 2024 16:42
@arjun024 arjun024 marked this pull request as ready for review April 30, 2024 16:42
@arjun024 arjun024 force-pushed the buildpacks-ci-push-repos branch from 2602461 to bb2f305 Compare April 30, 2024 16:45
@arjun024 arjun024 force-pushed the buildpacks-ci-push-repos branch from bb2f305 to b622817 Compare April 30, 2024 16:46
@stephanme
Copy link
Contributor

I merged this PR to unblock the buildpack CI and release process.

Long-term it is desirable to have branch protection enabled again. Can you double check which github user was used in the failed "put: ruby-buildpack-release" concourse task? Bot users like cf-buildpacks-eng should be able to commit directly to protected branches.

@stephanme stephanme merged commit d60aa8e into cloudfoundry:main May 2, 2024
2 checks passed
@sophiewigmore
Copy link
Member

Hey @stephanme, I just encountered the branch protection issue on another repository, and we are using the @cf-buildpacks-eng bot for pushing to main (see this failed run)

Are there any config files I need to modify to give the bot account the right permissions?

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

Successfully merging this pull request may close these issues.

4 participants