Tool-Cache getManifestFromRepo should use default branch or require a branch
Open
Nobody has claimed this yet.
enhancement
tool-cache
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the tool-cache's getManifestFromRepo defaults to the master branch if no branch is specified. Not every repo uses that as the default branch, we should try defaulting to the default branch, or just make users have to specify which branch to use.
Contributor guide
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 locating tool-cache's getManifestFromRepo and inspect how it chooses a branch when none is supplied. Check existing tests around manifest retrieval and determine whether the intended behavior is using the repository's default branch or requiring an explicit branch. Done means the non-master default-branch case is handled and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100