How to delete a branch from the Website repo

[JessicaLucindaCheng]

Overview

We need instructions for members of the website-admin team ¹ for deleting branches off the Website repo so that we do not have extraneous, unneeded branches.

Action Items

• Write instructions for how to delete a branch from the Website repo in a new comment below
• Add a link to the comment ² in the Resources/Instructions section
• In the Possible solutions [draft] section in ER: Developers are creating branches off hackforla/website #4876, find [Insert link to instructions] and replace it with the link to the comment with the instructions
• Once your issue has been approved, go to ER: Developers are creating branches off hackforla/website #4876 and
  • Check off this issue under the Dependency section
  • If all the issues in the Dependency section are checked off, move ER: Developers are creating branches off hackforla/website #4876 to New Issue Approval column and uncheck the Dependency label.
    • Click here to see how to uncheck the Dependency label

      

Resources/Instructions

Footnotes

1. website-admins team ↩

2. Link to instructions for how to delete a branch from the Website repo: ↩

[ExperimentsInHonesty]

• At the meeting yesterday, we decided that we do need an issue template for deleting branches
  • It would get used by people who wanted to report a branch that needed to be removed, but who don't have admin permission on the repo.
  • It would have the default label role: dev lead

[JessicaLucindaCheng]

• Progress: Depending on the answer to blocker, I still need to write a decision record on why we no longer need instructions for junior devs to delete branches because I changed permissions so website-merge team has explicit access to create a branch. Also, by GitHub's default settings, teams with admin or maintain roles (so for the website repo, website-admins team and website-maintain team respectively) can also create branches, though maintain may need to pass required checks to push.
• Blockers: We don't need instructions for how to delete branches for junior devs but should we still have instructions for website-admins team to delete branches created by them or Merge Team members?
  • Ans from Bonnie:

  • At the meeting yesterday, we decided that we do need an issue template for deleting branches
  • It would get used by people who wanted to report a branch that needed to be removed, but who don't have admin permission on the repo.
  • It would have the default label role: dev lead

• Availability: TBD
• ETA: TBD

[HackforLABot]

@JessicaLucindaCheng

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, November 25, 2024 at 11:04 PM PST.}