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

Create a wiki page for github-data GHA #3283

Closed
15 tasks done
Tracked by #3229
tamara-snyder opened this issue Jun 22, 2022 · 11 comments
Closed
15 tasks done
Tracked by #3229

Create a wiki page for github-data GHA #3283

tamara-snyder opened this issue Jun 22, 2022 · 11 comments
Assignees
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Wiki role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours Status: Updated No blockers and update is ready for review

Comments

@tamara-snyder
Copy link
Member

tamara-snyder commented Jun 22, 2022

Overview

As a developer, I would like to have up-to-date information about our GitHub actions in a wiki page. For this issue, we will create a Wiki page for the github-data GHA.

Action Items

  • Read the information about the github-data GHA here
  • Understand how the workflow operates
  • Add this new page in alphabetical order on the HfLA GitHub Actions Wiki Page.
  • Add the following information for the wiki page
    • Overview including definitions.
    • What does it do.
    • When does it trigger.
    • Discuss an example of a complete workflow cycle.
    • Other helpful information and related links
  • 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

Updated Wiki page

@tamara-snyder tamara-snyder added role: back end/devOps Tasks for back-end developers Feature: Wiki Complexity: Small Take this type of issues after the successful merge of your second good first issue size: 1pt Can be done in 4-6 hours labels Jun 22, 2022
@github-actions

This comment was marked as resolved.

@JessicaLucindaCheng JessicaLucindaCheng added the Draft Issue is still in the process of being created label Sep 19, 2022
@kathrynsilvaconway kathrynsilvaconway added Draft Issue is still in the process of being created and removed Draft Issue is still in the process of being created labels Oct 5, 2022
@kathrynsilvaconway

This comment was marked as resolved.

@JessicaLucindaCheng

This comment was marked as resolved.

@blulady blulady changed the title [DRAFT] Create a wiki page for github-data GHA Create a wiki page for github-data GHA Oct 24, 2022
@blulady blulady added Ready for Prioritization and removed Draft Issue is still in the process of being created labels Oct 24, 2022
@bishrfaisal bishrfaisal added this to the 08. Team workflow milestone Oct 30, 2022
@JessicaLucindaCheng
Copy link
Member

@bishrfaisal I saw you added a milestone and removed the Ready for Milestone label. Can this issue be prioritized in the Prioritized Backlog column yet?

@bishrfaisal
Copy link
Member

@JessicaLucindaCheng Yes, I went ahead and prioritized it in the Prioritized Backlog. Thanks for pointing that out.

@chrismenke45 chrismenke45 self-assigned this Jan 27, 2023
@github-actions
Copy link

Hi @chrismenke45, 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 :)

@github-actions
Copy link

@chrismenke45

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

You are receiving this comment because your last comment was before Monday, January 23, 2023 at 11:16 PM PST.

@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Jan 27, 2023
@chrismenke45
Copy link
Member

Availability: Friday 1/27 11am-3pm, Monday-Wednesday Flexible.
ETA: Wednesday 2/1 12pm.

@chrismenke45
Copy link
Member

Blocker: github-data GHA appears to not be in our repository anymore. This might be an outdated issue as it hasn't been updated for several months? I will ask leadership about this at a meeting.

@MattPereira MattPereira removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Feb 3, 2023
@github-actions github-actions bot added the Status: Updated No blockers and update is ready for review label Feb 3, 2023
@chrismenke45
Copy link
Member

I plan on reviewing my edits in office hours 2/9 7pm.
New ETA: Friday 2/10 3pm
Availability: Wed(2/8)-Thurs(2/9) 11am-3pm

@MattPereira
Copy link
Contributor

MattPereira commented Feb 10, 2023

@chrismenke45 great job communicating with us on this issue. 👍

Apologies about the confusion with the original state of the issue when you first picked it up.

The new GHA: github-data wiki page looks great! I like how you kept it concise with bullet points. Also appreciate the inclusion of the code block that shows the structure of each repo data object.

I did notice you forgot to include the worflow file that actually calls the get-project-data.js file on a schedule so I went ahead and added a link in the wiki for you

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: Wiki role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours Status: Updated No blockers and update is ready for review
Projects
Development

No branches or pull requests

7 participants