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

Creating issues: Review GHAs in wiki pages #3229

Closed
2 of 20 tasks
Tracked by #3227
SAUMILDHANKAR opened this issue Jun 7, 2022 · 5 comments
Closed
2 of 20 tasks
Tracked by #3227

Creating issues: Review GHAs in wiki pages #3229

SAUMILDHANKAR opened this issue Jun 7, 2022 · 5 comments
Labels
Added to dev/pm agenda Complexity: Medium Feature: Wiki Ignore: Duplicate Issue or pull request is a duplicate 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 role: dev leads Tasks for technical leads size: 1pt Can be done in 4-6 hours

Comments

@SAUMILDHANKAR
Copy link
Member

SAUMILDHANKAR commented Jun 7, 2022

Dependency

Overview

As a developer, I would like up to date information about our GitHub actions in a wiki page. For this epic, we will write issues to review and update wiki pages for each GitHub action which will then be added to dependency items above.

Action Items

  • This issue should only be assigned to a lead.
  • Read How to Contribute to the Wiki. When writing new issues to update the wiki, please keep the following in mind and consider adding something about it in the new issues created.
  • Lead would guide other developers on creating issues using the following steps (These steps would be recurring for each issue that would be created, and this action item should stay unchecked until all the issues have been created):
    • Check the following Google spreadsheet tab to track the issue creation progress. (there are 13 issues in total that need to be made)
    • Choose a row for which issue needs to be created and add your name in the Issue writer column. (If multiple team members creating issues simultaneously, let other team members know which row you would be working on, so there are no duplicate issues.) See column B to know if someone has started writing the issue already.
    • Write an issue with steps to review and update a wiki page following the sample issue below as well as using How to create issues wiki.
    • Update the issue link in the Google spreadsheet tab
  • Add the issue numbers of all the issues that have been created to the dependency section above as well as add ready for milestone labels on each of these issues if it looks good.
  • If all the issues for the spreadsheet tab have been created, add a dependency label and move this issue to ice box column.
  • If all the dependency issues are closed, remove the dependency label, move this issue from ice box to In progress column, check off the dependency from Creating issues: Review GHAs in wiki pages #3229 (if all the dependencies in Creating issues: Review GHAs in wiki pages #3229 are checked off, remove the dependency label, move Creating issues: Review GHAs in wiki pages #3229 issue from ice box to In progress column) and close this issue.

Resources/Instructions

Sample issue #3274

Overview

As a developer, I would like up to date information about our GitHub Actions in a wiki page. For this issue, we will review and update the wiki page for GHA: add update label weekly.

Action Items

  • Read the information about the add-update-label-weekly GHA here
  • Understand how the workflow works. Related files: move-closed-issues.yaml and sort-closed-issues.js
  • Review the information on the GHA: add update label weekly wiki page
  • Add or edit the following information for the GHA: add update label weekly wiki page for each of the following sections:
    • Summary (update overview, links, definitions for the GHA if possible). [Note: update the info here as well, if required]
    • Schedule (When does it trigger).
    • Workflow (Include the link to the workflow file as well as the process steps for a complete workflow cycle)
    • Supporting Files/Folder (Include links to the files or folders that are referenced in the workflow files as well as briefly describe the functionality of each file involved)
  • Reach out to the leads during the team meeting or on slack for a review since no PR would be required for this issue.
  • For reviewers: Once this issue has been reviewed and approved, please update and edit epic Creating issues: Review GHAs in wiki pages #3229 by

Resources/Instructions

@SAUMILDHANKAR SAUMILDHANKAR added role: back end/devOps Tasks for back-end developers Complexity: Medium Feature: Wiki size: 1pt Can be done in 4-6 hours labels Jun 7, 2022
@github-actions

This comment was marked as resolved.

@SAUMILDHANKAR SAUMILDHANKAR changed the title Creating issues: to document each GHA in a wiki page Creating issues: Document GHAs in a wiki page Jun 7, 2022
@SAUMILDHANKAR SAUMILDHANKAR changed the title Creating issues: Document GHAs in a wiki page Creating issues: Document GHAs in wiki pages Jun 21, 2022
@SAUMILDHANKAR SAUMILDHANKAR added Dependency An issue is blocking the completion or starting of another issue role: dev leads Tasks for technical leads and removed Dependency An issue is blocking the completion or starting of another issue labels Jun 21, 2022
@SAUMILDHANKAR SAUMILDHANKAR changed the title Creating issues: Document GHAs in wiki pages Creating issues: Review GHAs in wiki pages Jun 30, 2022
@mjh-projects mjh-projects reopened this Mar 29, 2023
@vincentdang

This comment was marked as outdated.

@GRK1998 GRK1998 self-assigned this Sep 5, 2023
@github-actions

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty moved this to In progress (actively working) in P: HfLA Website: Project Board Jun 23, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the ready for dev lead Issues that tech leads or merge team members need to follow up on label Aug 13, 2024
@ExperimentsInHonesty
Copy link
Member

This might be a duplicate of another issue. If it is, close it if appropriate.

@ExperimentsInHonesty ExperimentsInHonesty moved this from In progress (actively working) to New Issue Approval in P: HfLA Website: Project Board Aug 13, 2024
@roslynwythe
Copy link
Member

@roslynwythe roslynwythe closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2024
@github-project-automation github-project-automation bot moved this from New Issue Approval to QA in P: HfLA Website: Project Board Sep 16, 2024
@kgold2018 kgold2018 added the Ignore: Duplicate Issue or pull request is a duplicate label Sep 29, 2024
@kgold2018 kgold2018 moved this from QA to Done in P: HfLA Website: Project Board Sep 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Added to dev/pm agenda Complexity: Medium Feature: Wiki Ignore: Duplicate Issue or pull request is a duplicate 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 role: dev leads Tasks for technical leads size: 1pt Can be done in 4-6 hours
Projects
Development

No branches or pull requests

8 participants