Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ER: update the pr template #6058

Closed
2 of 5 tasks
ExperimentsInHonesty opened this issue Jan 3, 2024 · 12 comments
Closed
2 of 5 tasks

ER: update the pr template #6058

ExperimentsInHonesty opened this issue Jan 3, 2024 · 12 comments
Assignees
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Complexity: Small Take this type of issues after the successful merge of your second good first issue ER Emergent Request Feature: Standards Issue Making: Level 2 Make issue(s) from an ER or Epic role: back end/devOps Tasks for back-end developers size: 0.25pt Can be done in 0.5 to 1.5 hours

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jan 3, 2024

Emergent Requirement - Problem

We have observed non-members creating PRs. To solve this, we will add a notice to the top of the the PR template that notifies developers that they must complete onboarding before creating a PR.

Issue you discovered this emergent requirement in

Date discovered

2024-01-03

Did you have to do something temporarily

  • YES
  • NO

Who was involved

@ExperimentsInHonesty

What happens if this is not addressed

Non-members will continue to create PRs before completing onboarding.

Resources

None

Recommended Action Items

  • Make a new issue
  • Discuss with team
  • Let a Team Lead know

Potential solutions [draft]

Add the following text to add to to top of pull_request_template.md:

Please note: You must be a member of the HFLA  website team in order to create pull requests. Please see our page on how to join us as a member at HFLA: https://www.hackforla.org/getting-started.   Delete this message if you joined this team via onboarding.

When you make the issue, you will need to include some information on how to test the template.

@ExperimentsInHonesty ExperimentsInHonesty added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: 0.25pt Can be done in 0.5 to 1.5 hours role missing Complexity: Missing ER Emergent Request labels Jan 3, 2024
@github-actions github-actions bot removed the ER Emergent Request label Jan 3, 2024
@ExperimentsInHonesty ExperimentsInHonesty added this to the 08. Team workflow milestone Jan 3, 2024
@ExperimentsInHonesty ExperimentsInHonesty added Issue Making: Level 2 Make issue(s) from an ER or Epic Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Feature: Standards role: back end/devOps Tasks for back-end developers ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Complexity: Missing Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing labels Jan 3, 2024
@JessicaLucindaCheng JessicaLucindaCheng added the ER Emergent Request label Jan 26, 2024
@ExperimentsInHonesty

This comment was marked as resolved.

@gaylem gaylem self-assigned this Apr 12, 2024

This comment was marked as resolved.

@gaylem

This comment was marked as resolved.

@ExperimentsInHonesty

This comment was marked as resolved.

@gaylem gaylem removed their assignment Apr 16, 2024
@gaylem gaylem added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Apr 16, 2024
@ExperimentsInHonesty ExperimentsInHonesty added Complexity: Small Take this type of issues after the successful merge of your second good first issue and removed Ready for Prioritization labels Apr 16, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this to ERs and epics that are ready to be turned into issues in P: HfLA Website: Project Board Jun 23, 2024
@siyunfeng siyunfeng self-assigned this Nov 14, 2024
@HackforLABot
Copy link
Contributor

Hi @siyunfeng, 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 :)

@siyunfeng
Copy link
Member

Availability: 6-10 PM Weekdays (EDT)
ETA: 11/17/2024 Sunday

@t-will-gillis
Copy link
Member

@ExperimentsInHonesty @siyunfeng

I was pinged when this ER was assigned. Since the time of Bonnie's note above...

for now, just the notice. If in the future the problem is not solved by the notice, then we will write a GHA.

…we do have a functioning GHA that prevents non-members from submitting PRs:

This is only an FYI: we may still want to include the notice shown on this ER on the PR template.

@siyunfeng
Copy link
Member

@ExperimentsInHonesty @siyunfeng

I was pinged when this ER was assigned. Since the time of Bonnie's note above...

for now, just the notice. If in the future the problem is not solved by the notice, then we will write a GHA.

…we do have a functioning GHA that prevents non-members from submitting PRs:

This is only an FYI: we may still want to include the notice shown on this ER on the PR template.

Hi @t-will-gillis , I also noticed that the related issue to make a GHA was created and resolved.

Bonnie required me to work on creating this issue at the meeting on Tuesday. I went through this ER and did not see the notice in the PR template, so I assigned myself to work on it.

@ExperimentsInHonesty , should I continue working on creating an issue to add the notice in the PR template?

@siyunfeng siyunfeng moved this from ERs and epics that are ready to be turned into issues to In progress (actively working) in P: HfLA Website: Project Board Nov 15, 2024
@siyunfeng siyunfeng added the Status: Help Wanted Internal assistance is required to make progress label Nov 15, 2024
@siyunfeng
Copy link
Member

siyunfeng commented Nov 16, 2024

Hi @ExperimentsInHonesty , @t-will-gillis ,

I created a new issue for this ER:

I added Complexity: Small, role: back end/devOps, and Feature: Board/GitHub Maintenance to the issue.
Please correct me if I need to change them, and what should I add to the label for size?

@siyunfeng siyunfeng moved this from In progress (actively working) to Questions / In Review in P: HfLA Website: Project Board Nov 16, 2024
@siyunfeng siyunfeng removed the Status: Help Wanted Internal assistance is required to make progress label Nov 20, 2024
@siyunfeng
Copy link
Member

Provide Update

  1. Progress: Created the issue based on this ER
  2. Blockers: I'm still waiting for the merge team to review and approve issue Update PR Template with adding a notice of completing onboarding before creating a PR #7722
  3. Availability: 6-10 PM Weekdays (EDT)
  4. ETA: 11/24/2024 Sunday (once the issue is approved)

@roslynwythe
Copy link
Member

roslynwythe commented Nov 23, 2024

@siyunfeng
Copy link
Member

Hi @roslynwythe , thank you for reviewing the issue #7722 . I just updated the order of the instructions.
Can you review the issue again? Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Complexity: Small Take this type of issues after the successful merge of your second good first issue ER Emergent Request Feature: Standards Issue Making: Level 2 Make issue(s) from an ER or Epic role: back end/devOps Tasks for back-end developers size: 0.25pt Can be done in 0.5 to 1.5 hours
Projects
Development

No branches or pull requests

7 participants