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.

Sign up for GitHub

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

Jump to bottom

Edits to "Issue Trigger" workflow to exclude closed issues from assignee checks #7771

Open
1 task done
t-will-gillis opened this issue Nov 26, 2024 · 1 comment · May be fixed by #7817
Open
1 task done

Edits to "Issue Trigger" workflow to exclude closed issues from assignee checks #7771

t-will-gillis opened this issue Nov 26, 2024 · 1 comment · May be fixed by #7817
Assignees
@t-will-gillis
Labels
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

Comments

@t-will-gillis
Copy link
Member

t-will-gillis commented Nov 26, 2024 •
edited
Loading

Overview

We need our workflows to be adaptable to our use cases. The "Issue Trigger" workflow needs to be edited so that members can be assigned to closed issues without triggering the exclusion automation.

Action Items

Refer to the file check-complexity-eligibility.js
REVISED: Refer to the file preliminary-update-comment.js

  • Add a case that excludes any issues that are closed

Resources/Instructions
@t-will-gillis t-will-gillis added role: back end/devOps Tasks for back-end developers 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 size: 3pt Can be done in 13-18 hours Draft Issue is still in the process of being created labels Nov 26, 2024
@t-will-gillis t-will-gillis self-assigned this Nov 26, 2024
@HackforLABot

This comment was marked as resolved.

Sign in to view
@t-will-gillis t-will-gillis linked a pull request Jan 6, 2025 that will close this issue
Open
5 tasks
@t-will-gillis t-will-gillis removed the Draft Issue is still in the process of being created label Jan 6, 2025
@t-will-gillis t-will-gillis moved this from New Issue Approval to In progress (actively working) in P: HfLA Website: Project Board Jan 6, 2025
@t-will-gillis t-will-gillis mentioned this issue Jan 26, 2025
Closed
46 tasks
@t-will-gillis t-will-gillis added Complexity: Large and removed Complexity: Small Take this type of issues after the successful merge of your second good first issue labels Jan 28, 2025
@t-will-gillis t-will-gillis changed the title Edits to "Issue Trigger" workflow, check-complexity-eligibility.js Edits to "Issue Trigger" workflow to exclude closed issues from assignee checks Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@t-will-gillis t-will-gillis

Labels
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
Projects
P: HfLA Website: Project Board
Status: In progress (actively working)
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Edit to "Issue Trigger" workflow to exclude closed issues from assignee checks t-will-gillis/website
2 participants
@t-will-gillis @HackforLABot