microsoft / microsoft/msix-packaging
unhardcode master
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 193
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
Hardcoding references to the master branch, breaks modern Git FLow practices.
For forks, as well as for direct maintainers.
Propose moving the large/complex test fixtures from awkward git LFS to a more appropriate location, such as a CDN.
Relates to https://github.com/microsoft/msix-packaging/issues/694
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
No files, tests, or entry points are named. Begin by locating references to the master branch and the large or complex Git LFS fixtures, then review related issue #694; the scope is complete only when the branch assumptions and fixture-location approach are defined and addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100