Repository navigation
ci: remove obsolete OCP auto-approve workflow - #158
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Remove the legacy
update-nextcloud-ocp-approve-merge.ymlworkflow.The current Nextcloud organization template for this filename is now an explicit failing no-op with instructions to remove it because approval/auto-merge was folded into the newer OCP update workflows.
In
LibreCodeCoop/extractthere is no correspondingupdate-nextcloud-ocp.ymlorupdate-nextcloud-ocp-matrix.yml; repository search finds only this legacy approval workflow.Keeping the old file therefore provides no active update path while retaining a
pull_request_targetworkflow with write permissions and auto-approval/auto-merge behavior.This PR removes that obsolete surface instead of migrating it into the shared workflow platform.