Check origin prior to release
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 459
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
So I just went to release a version of a bundle/project that we don't often have to change anything. In any case we didn't git pull prior to making a release. Then the release failed. It would be useful to do a git fetch to ensure whatever branch we're on is updated prior to committing / modifying the changelog or other post release functions.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the release flow and the existing Git operations around changelog updates and other post-release functions. Check how the current branch is handled, then verify that the release process fetches from the origin before making those changes and that the release still completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, php
- Domain
- cli, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100