cloudfoundry / cloudfoundry/multiapps-cli-plugin
Rename sensitive naming from CI/CD infrastructure (e.g. master branch name)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 87
- Forks
- 42
- Avg merge
- 17d 21h
- Merged PRs (30d)
- 1
Description
In effort to align with the community guidelines, the codebase and supporting infrastructure should be manually analysed and all inappropriately named artefacts should be renamed.
One such example is the name of the "master" branch used in the 3 repositories of the multi apps project
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 inventorying the codebase and supporting infrastructure for the three repositories in the multi-apps project, including the referenced "master" branch name. Identify all artefacts covered by the community guidelines and map their references before changing names. Done means inappropriate names are renamed consistently across the repositories and infrastructure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100