Open roslynwythe opened 1 year ago
Hi @roslynwythe, thank you for taking up this issue! Hfla appreciates you :)
Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)
You're awesome!
P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)
@JessicaLucindaCheng - I believe you have prevented future branches off hackforla/website. Can you advise whether we still need this ER?
@roslynwythe
@JessicaLucindaCheng - I believe you have prevented future branches off hackforla/website. Can you advise whether we still need this ER?
Before I can answer that, I have a question. Since merge team members can create branches but I don't think they can delete them, how will we know when a branch created by a merge team member needs to be deleted?
@JessicaLucindaCheng We can create an issue template I have updated the potential solution draft above and added check boxes. Are you ready for me to prioritize this?
Hi @JessicaLucindaCheng, thank you for taking up this issue! Hfla appreciates you :)
Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)
You're awesome!
P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)
@ExperimentsInHonesty
@JessicaLucindaCheng We can create an issue template I have updated the potential solution draft above and added check boxes. Are you ready for me to prioritize this?
Yes, it's ready to be prioritized. Please note that I made some edits to the Potential Solutions (draft) section and changed the feature label.
@JessicaLucindaCheng I updated the possible solutions template part. From
Write an issue for a back-end developer to work on creating an issue template for reporting that a branch created by the Merge Team needs to be removed.
to
Write an issue for a back-end developer to work on creating an issue template for reporting that a branch created by the Merge Team needs to be removed. The issue template can be the report and the instructions for removing all in one.
If you agree, add ready for prioritization label, otherwise leave comment.
@ExperimentsInHonesty
@JessicaLucindaCheng I updated the possible solutions template part. From
Write an issue for a back-end developer to work on creating an issue template for reporting that a branch created by the Merge Team needs to be removed.
to
Write an issue for a back-end developer to work on creating an issue template for reporting that a branch created by the Merge Team needs to be removed. The issue template can be the report and the instructions for removing all in one.
If you agree, add ready for prioritization label, otherwise leave comment.
- [ ] Write an issue for a back-end developer to work on creating an issue template that includes both:
- [ ] A section for reporting that a branch created on the Website repo needs to be removed
- [ ] A section with instructions for how to remove the branch.
- [ ] Instructions can be copied and pasted from [Insert link to instructions] into the issue template
ready for product
label ready for dev lead
labelready for prioritization
. Add a ready for prioritization
label.
Dependency
Emergent Requirement - Problem
Developers inadvertently create extraneous branches off the hackforla/website repository (instead of creating branches on their fork) but they do not have rights to delete the extraneous branches. We need to prevent developers from creating these branches, and we require an issue template for instances for use when such a branch has been created and needs to be deleted.
Issue you discovered this emergent requirement in
Date discovered
discussed at meeting 6/12/2023
Did you have to do something temporarily
We are currently pruning the branches manually, which is a waste of time.
Who was involved
Bonnie Wolfe, @JessicaLucindaCheng
What happens if this is not addressed
The branches will persist until deleted by a lead and the lead will need to figure out which branches can be deleted, which can take a lot of time and research.
Resources
Recommended Action Items
Potential solutions [draft]
[x] prevent write members who are not part of merge team from creating branches
@JessicaLucindaCheng implemented the solution for preventing members (aside from merge team) from creating branches off hackforla/website in the future by doing the following:
Click here to see the detailed instructions
[ ] Write an issue for a back-end developer to work on creating an issue template that includes both: