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

Update "Schedule Monthly" workflow for updated meeting #7870

Open
5 tasks done
t-will-gillis opened this issue Feb 1, 2025 · 1 comment · May be fixed by #7871
Open
5 tasks done

Update "Schedule Monthly" workflow for updated meeting #7870

t-will-gillis opened this issue Feb 1, 2025 · 1 comment · May be fixed by #7871
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: 0.25pt Can be done in 0.5 to 1.5 hours time sensitive Needs to be worked on by a particular timeframe

Comments

@t-will-gillis
Copy link
Member

t-will-gillis commented Feb 1, 2025

Overview

The previous Monday meeting agenda has been retired and replaced. We need to update the agenda number on the "Schedule Monthly" workflow, and move this variable to the global scope so that it is more easily found in the future.

Action Items

  • In the file create-new-issue.js, insert the following after the // Globel variables comment:
    const AGENDA_ISSUE_NUM = 7859;            // Issue number of the Dev/PM meeting agenda on Mondays
    
  • Add JSDoc comments for main() function
  • Delete:
      const agendaIssueNum = 2607;            // Issue number of the Dev/PM meeting agenda on Mondays
    
  • Replace:
      await postComment(agendaIssueNum, commentBody, github, context);
    
    with:
      await postComment(AGENDA_ISSUE_NUM, commentBody, github, context);
    
  • Although this issue involves GitHub Actions, full testing is not required.

Resources/Instructions

@t-will-gillis t-will-gillis added 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: 0.25pt Can be done in 0.5 to 1.5 hours time sensitive Needs to be worked on by a particular timeframe labels Feb 1, 2025
@t-will-gillis t-will-gillis self-assigned this Feb 1, 2025
@github-project-automation github-project-automation bot moved this to New Issue Approval in P: HfLA Website: Project Board Feb 1, 2025
@HackforLABot
Copy link
Contributor

Hi @t-will-gillis, we notice that you are assigned to an issue that you authored. Please remember to add the Draft label to this issue while you are working on it.

@t-will-gillis t-will-gillis added Draft Issue is still in the process of being created and removed Draft Issue is still in the process of being created labels Feb 1, 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 1, 2025
@t-will-gillis t-will-gillis linked a pull request Feb 1, 2025 that will close this issue
5 tasks
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: 0.25pt Can be done in 0.5 to 1.5 hours time sensitive Needs to be worked on by a particular timeframe
Projects
Status: In progress (actively working)
Development

Successfully merging a pull request may close this issue.

2 participants