Skip to content

Conversation

@t-will-gillis
Copy link
Member

@t-will-gillis t-will-gillis commented Aug 10, 2025

Fixes #8259

What changes did you make?

Temporary files and edits (to be removed after project is done)

  • In activity-history-post.yml, edited cron to trigger a second time
  • In first-post-to-skills-issue.js:
    • changed trigger doc,
    • reordered parameters to postComment(),
    • added call to clean up bot comments
  • Added get-issue-comments.js
  • Modified member_activity_history_bot_<x>
    Permanent files and edits
  • Added section to add-label.js to exclude MARKER
  • Added new label SkillsIssueCompleted

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

  • Cron was edited to be triggered a second time
  • Reordered paraments to postComment() to match the (backwards) current params
  • Added functionality to minimize comments while adding the new bot comment
  • Added permanent changes for "Schedule Friday" workflow:
    • to ignore any bot comment that includes MARKER - thus not minimizing it
    • to ignore posting update requests (2 weeks inactive, etc.) to issues labeled Skills Issue Completed

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.

Check the PR's comments. If present on your PR, the CodeQL alert looks similar as shown

Screenshot 2024-10-28 154514

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)
Instructions for resolving CodeQL alerts

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)

  • No visual changes

@github-actions
Copy link

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-adjust-initial-skills-issue-post gh-pages
git pull https://github.com/t-will-gillis/website.git adjust-initial-skills-issue-post

@t-will-gillis t-will-gillis merged commit ca2eedd into hackforla:gh-pages Aug 10, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Development

Successfully merging this pull request may close these issues.

GHA to Document Previous Issue Event on Skills Issue, Pt 3

1 participant