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 check-linked-issue.js #1019

Open
wants to merge 1 commit into
base: refactor-pr-trigger-check
Choose a base branch
from

Conversation

t-will-gillis
Copy link
Owner

Fixes #replace_this_text_with_the_issue_number

What changes did you make?

Why did you make the changes (we will use this info to test)?

Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)

Visuals before changes are applied

image

Visuals after changes are applied

image

Copy link

github-actions bot commented Oct 6, 2024

@t-will-gillis, this Pull Request is not linked to a valid issue. Above, on the first line of your PR, please link the number of the issue that you worked on using the format of 'Fixes #' + issue number, for example: Fixes #9876

Note: Do not use the number of this PR.

Copy link

github-actions bot commented Oct 6, 2024

Want to review this pull request? Take a look at this documentation for a step by step guide!


From your project repository, check out a new branch and test the changes.

git checkout -b t-will-gillis-t-will-gillis-patch-3 refactor-pr-trigger-check
git pull https://github.com/t-will-gillis/website.git t-will-gillis-patch-3

Copy link

github-actions bot commented Oct 6, 2024

@t-will-gillis, this Pull Request is not linked to a valid issue. In the Pull Request body above, you must link the number of the issue that you worked on using the format of 'Fixes #' + issue number, for example: Fixes #0000

Note: Do not use the number of this PR.

@t-will-gillis
Copy link
Owner Author

Fixes #replace_this_text_with_the_issue_number

What changes did you make?

Why did you make the changes (we will use this info to test)?

CodeQL Alerts

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

A bot comment might mention a CodeQL alert

Screenshot 2024-10-15 153738

If your issue has a CodeQL alert and is complexity: medium or higher, please let us know that you have checked and resolved. Please do not dismiss alerts.

  • I have checked this PR for CodeQL alerts. If CodeQL alerts were found:
    • I have resolved CodeQL alerts
    • I believe this CodeQL alerts is a false positive (merge team will evaluate)
    • I am stuck (after reading instructions below)
Instructions

If CodeQL alert/annotations appear, refer to How to Resolve CodeQL alerts.

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

Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)

Visuals before changes are applied

image

Visuals after changes are applied

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: PR Needs review (Automated Column, do not place items here manually)
Development

Successfully merging this pull request may close these issues.

1 participant