ER: New Wiki Content for large issues

[ExperimentsInHonesty]

trafficstars

Dependency

• #3635
• #3636

Overview

We need to add new content to the wiki so that it can help people do larger issues

Action Items

• [ ] We are currently in the process of moving the old wiki to the new website-wiki repo, so we will not be making any changes or additions to the old wiki at this time. Thus, we will be adding wiki content through a different process now. Read How to Contribute to the Wiki
• [ ] Create issues to write the content

Resources/Instructions

Issues that could have used the documentation

• #1445
• #1892

Content

• Graph QL
• Using GitHub Actions at Hack for LA (in addition to GitHub's link)
• Using GitHub Artifacts (link to Github)
• Finding and Access Logs for GitHub Actions

[ExperimentsInHonesty]

I anticipate that someone from the @hackforla/website-merge team will make these issues.

[JessicaLucindaCheng]

This issue needs to be edited by a lead to reflect our migration to the website-wiki repo. For more info, read How to Contribute to the Wiki.

[ExperimentsInHonesty]

@roslynwythe I moved this into the new issue review column because the dependency is resolved. Please add a ready for prioritization label if its ready.

[ExperimentsInHonesty]

@hackforla/website-merge Can someone from the merge team review this ER and if you think it is ready for issue making, please add a ready for prioritization label.

[ExperimentsInHonesty]

I am not sure what size issues would be made. And if there is enough information in this ER for a clear direction forward. Looking for some feedback from merge team.

[roslynwythe]

• @ExperimentsInHonesty I suggest incorporating the desired issues into #6403 which already included plans to review/enhance documentation for pr-labels

[ExperimentsInHonesty]

• @roslynwythe ok, sounds good. Go ahead and close this issue as unplanned when #6403 is updated.

[HackforLABot]

Hi @roslynwythe, HfLA appreciates your interest in this issue, but please note that it is in the "New Issue Approval" column of the Project Board because it has not been finalized, approved, or prioritized, and so it is not ready for assignment. For this reason, you have been unassigned from this issue. Please remember to assign issues only from the "Prioritized Backlog" column.

The only exceptions to this rule are if you are writing an issue and the Draft label is applied, or if you are self-assigning to your "Pre-work Checklist" (the issue includes the Complexity: Prework label).

[ExperimentsInHonesty]

confirmed on 2024-09-16 @roslynwythe will add the items from this issue to

• #6403