Skip to content

Modify the release process to avoid branch protection errors #81

@NickLarsenNZ

Description

@NickLarsenNZ

When running the release-tag task, we encounter an error:

./release/create-release-tag.sh -t 24.7.0 -w products -p
remote: error: GH006: Protected branch update failed for refs/heads/release-24.7.
remote: error: Changes must be made through a pull request.

We propose updating the process to:

  • raise Pull Requests for (changelog update) commit to the release branch.
  • tag the merge commit after the PR is merged
    • This could be a github action, so that it is automatic.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions