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

Verify dependabot version updates to GHAs for issue-trigger.yml #4822

Closed
3 of 7 tasks
t-will-gillis opened this issue Jun 13, 2023 · 3 comments · Fixed by #4905
Closed
3 of 7 tasks

Verify dependabot version updates to GHAs for issue-trigger.yml #4822

t-will-gillis opened this issue Jun 13, 2023 · 3 comments · Fixed by #4905
Assignees
Labels
Complexity: Medium Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours

Comments

@t-will-gillis
Copy link
Member

t-will-gillis commented Jun 13, 2023

Prerequisites

  1. You must be a member of Hack for LA to work on an issue. If you have not joined yet, please follow the steps on our Getting Started page.
  2. Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.

Overview

Our repo's dependabot has been identifying the packages/dependencies for which a more recent version is available, and for each it has created a PR detailing which files in our codebase use that package/dependency. We need to check each of these files individually to determine whether we should or should not switch to the latest version.

Action Items

Refer to the issue-trigger.yml file and review with the version updates recommended by the dependabot.
Select:

Merge team:

Resources/Instructions

@t-will-gillis t-will-gillis added Complexity: Medium Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms role: back end/devOps Tasks for back-end developers size: 1 pt Draft Issue is still in the process of being created labels Jun 13, 2023
@t-will-gillis
Copy link
Member Author

Issue #4189 might be updating the versions per 4734, 4735, 4737: If so this issue will be unnecessary. If not then issue should proceed.

@t-will-gillis t-will-gillis self-assigned this Jun 29, 2023
@github-actions
Copy link

Hi @t-will-gillis, 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 :)

@t-will-gillis
Copy link
Member Author

Issue #4189 will be closed, with this issue taking over.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours
Projects
Development

Successfully merging a pull request may close this issue.

3 participants