Add main branch test that simulates the VERSION file introduced when RCs are released
Open
Nobody has claimed this yet.
Test
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
We might be able to detect these sooner by specifically running tests in microsoft/main with a fake VERSION file:
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 reviewing the microsoft/main test setup and the referenced pull request 1537 and issue 68579. Add a test scenario with a fake VERSION file representing the file introduced during RC releases, then run the relevant main-branch tests to confirm this situation is detected earlier.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100