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

Fix the Add-Missing-Labels-to-Issues job error #4189

Closed
10 tasks
jdingeman opened this issue Mar 15, 2023 · 27 comments
Closed
10 tasks

Fix the Add-Missing-Labels-to-Issues job error #4189

jdingeman opened this issue Mar 15, 2023 · 27 comments
Labels
Complexity: Large Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers size: 3pt Can be done in 13-18 hours

Comments

@jdingeman
Copy link
Member

jdingeman commented Mar 15, 2023

Overview

Dev leads have noticed that the Add-Missing-Labels-to-Issues job is failing whenever we submit a new issue onto the project board. We need to correct the job so that it works correctly and adds missing labels to issues that are submitted for approval.

Action Items

Resources/Instructions

@jdingeman jdingeman added role: back end/devOps Tasks for back-end developers Complexity: Large Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms ready for dev lead Issues that tech leads or merge team members need to follow up on size: 3pt Can be done in 13-18 hours labels Mar 15, 2023
@JessicaLucindaCheng

This comment was marked as outdated.

@jdingeman

This comment was marked as outdated.

@jdingeman

This comment was marked as outdated.

@jdingeman jdingeman added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Mar 23, 2023
@ExperimentsInHonesty

This comment was marked as resolved.

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Ready for Prioritization labels Mar 23, 2023
@jdingeman jdingeman added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Mar 23, 2023
@jdingeman

This comment was marked as outdated.

@ExperimentsInHonesty

This comment was marked as resolved.

@jdingeman

This comment was marked as resolved.

@github-actions

This comment was marked as outdated.

@richardmundyiii

This comment was marked as outdated.

@github-actions github-actions bot added the To Update ! No update has been provided label Apr 7, 2023
@jdingeman

This comment was marked as outdated.

@github-actions github-actions bot added To Update ! No update has been provided 2 weeks inactive An issue that has not been updated by an assignee for two weeks and removed Status: Updated No blockers and update is ready for review To Update ! No update has been provided labels Apr 21, 2023
@roslynwythe

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label May 15, 2023
@EdASalazar EdASalazar self-assigned this Jun 7, 2023
@github-actions

This comment was marked as outdated.

@EdASalazar

This comment was marked as outdated.

@t-will-gillis
Copy link
Member

Hello @EdASalazar
In case you did not see this, we implemented a new dependabot a couple of weeks ago that searches through our codebase looking for action modules that have older version numbers. The bot is recommending that we update various versions listed in the issue-trigger.yml file:

It will be a good idea to make these version changes to your test files right away, since a. we will need to update these versions very soon and b. the new versions (esp get-user-teams-membership) might eliminate some of the errors that are occurring.

Let us know if you would like to talk about this more and/or have blockers. Thanks!

@EdASalazar

This comment was marked as outdated.

@t-will-gillis
Copy link
Member

It will be a good idea to make these version changes to your test files right away, since a. we will need to update these versions very soon and b. the new versions (esp get-user-teams-membership) might eliminate some of the errors that are occurring.

As I am testing other GHAs for the dependabot-suggested version update changes: I believe that the updates suggested in issue 4734 might/will break this GHA and should not be done.

@EdASalazar

This comment was marked as outdated.

@t-will-gillis

This comment was marked as outdated.

@EdASalazar
Copy link
Member

Hi @EdASalazar - you might check the Settings General in your repo and scroll down to Features and check if the Issues box is checked:

That was it. Thank you so much! I was losing my mind.

@EdASalazar EdASalazar removed their assignment Jun 26, 2023
@t-will-gillis

This comment was marked as outdated.

@roslynwythe roslynwythe added the ready for dev lead Issues that tech leads or merge team members need to follow up on label Jun 29, 2023
@t-will-gillis
Copy link
Member

It appears that this issue has been resolved by regenerating the secrets.TEAMS tokens. Issue #4822 will check the next steps needed for reviewing the "Add-Missing-Labels-to-Issues" job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms ready for dev lead Issues that tech leads or merge team members need to follow up on 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

7 participants