jakartaee / jakartaee/platform
Mitigate impact of changing master to main
- Dominant language
- No language data
- Stars
- 230
- Forks
- 77
- Avg merge
- 8d 5h
- Merged PRs (30d)
- 1
Description
@edburns requested branch **master** rename to **main** before proper notification.
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/3122
This issue seeks to identify collect, and track the mitigation of anything that breaks as a result of this change.
[AB#48](https://dev.azure.com/jakarta-ee-azdo/7cf9a9d3-9854-41e0-9a66-99506a9ed874/_workitems/edit/48)
Contributor guide
Research direction
Start by reviewing the linked Eclipse Foundation helpdesk issue 3122 and Azure Boards work item AB#48, then inspect the repository workflows and references affected by the master-to-main rename. Done means the resulting breakages are identified, collected, and tracked with mitigation status; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100