docs: Improved parsing of upstream branch name by bartdorlandt · Pull Request #1328 · python-semantic-release/python-semantic-release
When using renovate it may present branch names with additional "." (dots) in the branch name. This will break the upstream branch lookup. This updated version focuses on the 3 consecutive dots instead.
Purpose
Improve docs example on github CI pipeline, specifically on locating the upstream branch.
Rationale
When using renovate it may present branch names with additional "." (dots) in the branch name. This will break the upstream branch lookup. This updated version focuses on the 3 consecutive dots instead and selects the upstream branch name.
How did you test?
I changed the code in my own pipeline.
https://github.com/bartdorlandt/convert_poetry2uv/pull/44/files
How to Verify
Execute the old and new command on upstream branches, one with a "." in the name and one without.
PR Completion Checklist
- Reviewed & followed the Contributor Guidelines
note: the link doesn't function anymore.
-
Changes Implemented & Validation pipeline succeeds
-
Commits follow the Conventional Commits standard
and are separated into the proper commit type and scope (recommended order: test, build, feat/fix, docs) -
Appropriate Unit tests added/updated
-
Appropriate End-to-End tests added/updated
-
Appropriate Documentation added/updated and syntax validated for sphinx build (see Contributor Guidelines)