Skip to content

Commit

Permalink
Merge branch 'gh-pages' into maint-adj-sch-monthly-7614
Browse files Browse the repository at this point in the history
  • Loading branch information
t-will-gillis authored Nov 1, 2024
2 parents e889ac3 + c2b1c22 commit 7144fbe
Show file tree
Hide file tree
Showing 8 changed files with 1,516 additions and 1,293 deletions.
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/add-github-handle.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ name: github-handle in project file
about: For adding github-handle to member data in a project file
title: Add github-handle for [INSERT NAME] in [INSERT PROJECT FILE]
labels: 'Complexity: Small, feature: spelling, good first issue, P-Feature: Project
Info and Page, ready for dev lead, role: back end/devOps, role: front end, size:
Info and Page, ready for merge team, role: back end/devOps, role: front end, size:
0.5pt, size: 0.25pt'
assignees: ''

Expand Down
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/img-tag-refactor-on-website.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ assignees: ''

### Prerequisite
1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our [Getting Started page](https://www.hackforla.org/getting-started) and attend an onboarding session.
2. Before you claim or start working on an issue, please make sure you have read our [How to Contribute to Hack for LA Guide](https://github.com/hackforla/website/blob/7f0c132c96f71230b8935759e1f8711ccb340c0f/CONTRIBUTING.md).
2. Before you claim or start working on an issue, please make sure you have read our [How to Contribute to Hack for LA Guide](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md).

### Overview
We want to change an img HTML tag ending with a slash (<img.../>) to an img tag without an ending slash (<img...>) so that the codebase is consistent with how we use img HTML tags.
Expand Down
28 changes: 28 additions & 0 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,34 @@ Fixes #replace_this_text_with_the_issue_number
-
-

<h3>CodeQL Alerts</h3>


After the PR has been submitted and the resulting GitHub actions/checks have been completed, developers should check the PR for CodeQL alert annotations.


<details><summary>Check the PR's comments. If present on your PR, the CodeQL alert looks similar as shown</summary>

![Screenshot 2024-10-28 154514](https://github.com/user-attachments/assets/ea66c586-c14c-45fd-8705-1c116224e704)


</details>

Please let us know that you have checked for CodeQL alerts. **Please do not dismiss alerts.**
- [ ] I have checked this PR for CodeQL alerts and none were found.
- [ ] I found CodeQL alert(s), and (select one):
- [ ] I have resolved the CodeQL alert(s) as noted
- [ ] I believe the CodeQL alert(s) is a false positive (Merge Team will evaluate)
- [ ] I have followed the Instructions below, but I am still stuck (Merge Team will evaluate)

<details><summary>Instructions for resolving CodeQL alerts</summary>

If CodeQL alert/annotations appear, refer to [How to Resolve CodeQL alerts](https://github.com/hackforla/website/issues/6463#issuecomment-2002573270).

In general, CodeQL alerts should be resolved prior to PR reviews and merging

</details>

### Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)
<!-- Notes:
- If there are no visual changes to the website, delete all of the script below and replace with "- No visual changes to the website"
Expand Down
1 change: 1 addition & 0 deletions .github/workflows/schedule-fri-0700.yml
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@ on:
jobs:
Add-Update-Label-to-Issues-Weekly:
runs-on: ubuntu-latest
if: github.repository == 'hackforla/website'
steps:
- uses: actions/checkout@v4
- uses: actions/github-script@v7
Expand Down
Loading

0 comments on commit 7144fbe

Please sign in to comment.