Rename and protect the default branch

Open
#95 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
git, github-actions
Domain
ci-cd, infrastructure

Research direction

Start by identifying the repository's GitHub Actions references to master and review the linked GitHub guidance for updating local clones. Coordinate the Apache infrastructure ticket for the branch rename and protection rules, then update the workflows and notify the dev list. Done means main is the default protected branch, Actions use main, and contributors have the local-update guidance.

Written by the indexing model from the issue text.

Description

process
  1. Rename the master branch to main so that this repo matches current defaults and is more welcoming to new contributors.
  2. Add branch protection rules to main that require a pull request with an approval to commit.
  3. Update GitHub actions to use main instead of master.
  4. Notify dev list to update their locals as such: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes

Steps 1 and 2 require an Apache infra ticket.

Dominant language
Jupyter Notebook
Stars
30
Forks
15
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/flagon

All issues in apache/flagon

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.