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

Change label for issues unassigned by bot to Status: Unassigned by Bot #7881

Closed
5 tasks done
t-will-gillis opened this issue Feb 4, 2025 · 4 comments · Fixed by #7933
Closed
5 tasks done

Change label for issues unassigned by bot to Status: Unassigned by Bot #7881

t-will-gillis opened this issue Feb 4, 2025 · 4 comments · Fixed by #7933
Assignees
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms role: back end/devOps Tasks for back-end developers size: 3pt Can be done in 13-18 hours time sensitive Needs to be worked on by a particular timeframe

Comments

@t-will-gillis
Copy link
Member

t-will-gillis commented Feb 4, 2025

Overview

Currently, the GitHub Actions automation bot unassigns devs from issues if either the devs should not be working on the issue, or if the issue is not ready to be worked on. The bot then labels and moves the issue to "New Issue Approval". We need to change the label that the bot applies so that these issues are easier to find.

Action Items

  • In the function handleIssueComplexityNotPermitted() in the file check-complexity-eligibility.js, replace:

      // Add 'Ready for Prioritization' label 
      await github.rest.issues.addLabels({
        owner,
        repo,
        issue_number: currentIssueNum,
        labels: ['Ready for Prioritization'],
      });
    

    with:

      // Add `Status: Unassigned by Bot` label 
      await github.rest.issues.addLabels({
        owner,
        repo,
        issue_number: currentIssueNum,
        labels: ['Status: Unassigned by Bot'],
      });
    
  • In the function main() in the file preliminary-update-comments.js, replace:

       const READY_FOR_PRIORITIZATION = "Ready for Prioritization";
    

    with:

        const STATUS_UNASSIGNED_BY_BOT = "Status: Unassigned by Bot";
    
  • and replace:

        await addLabel(READY_FOR_PRIORITIZATION);
        console.log(' - remove developer and add `Ready for Prioritization` label');
    

    with:

        await addLabel(STATUS_UNASSIGNED_BY_BOT);
        console.log(' - remove developer and label for re-prioritization');
    
  • Finally, in the label-directory.json file, replace:

      "NEW-statusUnassignedByBot": [
      "Status: Unassigned by Bot",
      8096814358
    ]
    

    with:

      "statusUnassignedByBot": [
      "Status: Unassigned by Bot",
      8096814358
    ]
    
  • Note: Although this issue involves GitHub Actions, testing of the GHA not required. The automation is known to work, and the issue is swapping out one existing label for another.

@t-will-gillis t-will-gillis added Complexity: Large Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms role: back end/devOps Tasks for back-end developers size: 3pt Can be done in 13-18 hours labels Feb 4, 2025
@github-project-automation github-project-automation bot moved this to New Issue Approval in P: HfLA Website: Project Board Feb 4, 2025
@t-will-gillis t-will-gillis added the time sensitive Needs to be worked on by a particular timeframe label Feb 4, 2025
@t-will-gillis t-will-gillis self-assigned this Feb 4, 2025
@t-will-gillis t-will-gillis moved this from New Issue Approval to In progress (actively working) in P: HfLA Website: Project Board Feb 4, 2025
@HackforLABot

This comment has been minimized.

@t-will-gillis

This comment has been minimized.

@HackforLABot HackforLABot added the To Update ! No update has been provided label Feb 14, 2025
@HackforLABot

This comment has been minimized.

@HackforLABot HackforLABot added 2 weeks inactive and removed To Update ! No update has been provided labels Feb 21, 2025
@HackforLABot

This comment has been minimized.

@t-will-gillis t-will-gillis added Complexity: Small Take this type of issues after the successful merge of your second good first issue and removed Complexity: Large 2 weeks inactive labels Feb 21, 2025
@github-project-automation github-project-automation bot moved this from In progress (actively working) to QA in P: HfLA Website: Project Board Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms role: back end/devOps Tasks for back-end developers size: 3pt Can be done in 13-18 hours time sensitive Needs to be worked on by a particular timeframe
Projects
Development

Successfully merging a pull request may close this issue.

2 participants