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: github-actions bot removing Draft label #3758

Closed
1 of 5 tasks
JessicaLucindaCheng opened this issue Nov 30, 2022 · 9 comments
Closed
1 of 5 tasks

ER: github-actions bot removing Draft label #3758

JessicaLucindaCheng opened this issue Nov 30, 2022 · 9 comments
Labels
automation for manulal github board maintenance actions that are going to be automated Complexity: Large ER Emergent Request Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly role: back end/devOps Tasks for back-end developers size: 3pt Can be done in 13-18 hours

Comments

@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Nov 30, 2022

Emergent Requirement - Problem

The github-actions bot is removing the Draft label. This happens when the Draft label is added after clicking the "Submit new issue" button.

Issue you discovered this emergent requirement in

Date discovered

November 21, 2022

Did you have to do something temporarily?

  • YES
  • NO

I had to reapply the "Draft" label.

Who was involved?

@JessicaLucindaCheng

What happens if this is not addressed

If the "Draft" label is removed by the bot and not reapplied by the issue writer, then it will require someone to take the time to read the issue to see the status of the issue and then reapply the "Draft" label.

Resources/Instructions

Recommended Action Items

Potential solutions [draft]

  • After discussion at the PM/Dev Lead meeting on March 27, 2023, it was determined that we will make new issues to add the labels that are part of the Missing series onto the templates so that the label exists on the issue already before the dev submits the new issue.
    • This won't solve the issue directly, but the idea is that we avoid the GitHub bot's intervention if the template already has the labels
    • Need to make a template for the issue
    • Make a bunch of good first/second issues to fix the issue templates
@JessicaLucindaCheng JessicaLucindaCheng added Complexity: Large Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly automation for manulal github board maintenance actions that are going to be automated role: dev leads Tasks for technical leads Draft Issue is still in the process of being created size: 0.25pt Can be done in 0.5 to 1.5 hours labels Nov 30, 2022
@JessicaLucindaCheng

This comment was marked as outdated.

@JessicaLucindaCheng JessicaLucindaCheng added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Draft Issue is still in the process of being created labels Dec 2, 2022
@MattPereira MattPereira self-assigned this Jan 10, 2023
@MattPereira MattPereira removed their assignment Feb 9, 2023
@ExperimentsInHonesty ExperimentsInHonesty added this to the 08. Team workflow milestone Mar 5, 2023
@jdingeman
Copy link
Member

It was discussed during the Tuesday planning meeting that this may not be fixable as it is a matter of us putting the labels against GitHub's API -- specifically when the issue creator puts a new label immediately after submitting the issue.

@jdingeman jdingeman added ready for product and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Mar 9, 2023
@ExperimentsInHonesty
Copy link
Member

@hackforla/website-merge So what are the next steps for this issue, should move it into prioritized backlog?

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed ready for product labels Mar 10, 2023
@jdingeman
Copy link
Member

@hackforla/website-merge - we need to discuss the possibility of having the templates already include the "Missing: " series to avoid situations of issue writers adding labels to an issue immediately after issue submission. That way since the template will come prefilled with the labels, the automation (ideally) won't try to take off the label upon submission.

@MattPereira
Copy link
Contributor

@hackforla/website-merge

I thought we discussed this issue of bot ripping off any label you add right after creation of an issue.

The github API is kinda slow and will just reject any labels if you add them too quickly after issue creation.

Its nothing we can fix with the code in our repository. My first large issue was this same problem but with the Ready for Milestone label and I spent months disappointed in myself that I couldn't solve it

I would hate for another dev to be given a mission impossible issue. It feels real bad.

@MattPereira
Copy link
Contributor

MattPereira commented Mar 22, 2023

having the templates already include the "Missing: " series to avoid situations of issue writers adding labels to an issue immediately after issue submission

This could potentially address the required size, complexity, and role labels but this ER is about the optional draft label

the automation (ideally) won't try to take off the label upon submission

I don't think the automation ever takes off labels that are already attatched prior to issue creation

@JessicaLucindaCheng JessicaLucindaCheng added role: back end/devOps Tasks for back-end developers size: 3pt Can be done in 13-18 hours and removed role: dev leads Tasks for technical leads size: 0.25pt Can be done in 0.5 to 1.5 hours labels Mar 23, 2023
@jdingeman jdingeman self-assigned this Mar 29, 2023
@github-actions

This comment was marked as outdated.

@jdingeman
Copy link
Member

jdingeman commented Mar 29, 2023

Started a new epic with issue template based off of our conversation about adding the Missing series labels to our issue templates:

@jdingeman jdingeman added ready for product and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Mar 31, 2023
@ExperimentsInHonesty
Copy link
Member

I have added the draft label to the ER that Justin opened above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation for manulal github board maintenance actions that are going to be automated Complexity: Large ER Emergent Request Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly role: back end/devOps Tasks for back-end developers size: 3pt Can be done in 13-18 hours
Projects
Development

No branches or pull requests

5 participants