Open roslynwythe opened 1 year ago
@ExperimentsInHonesty Please advise, if there is activity associated with a contributor but their prework issue is closed, should the prework issue be reopened?
@roslynwythe
@ExperimentsInHonesty Please advise, if there is activity associated with a contributor but their prework issue is closed, should the prework issue be reopened?
Yes!
Newly reopened issues should be placed in the In Progress column
RW: Done!
Hi @partapparam, 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 :)
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) 3pm - 6pm Thursday and Friday, 9am - 1pm Sunday, will update additional availability after Sunday ii. ETA: (When do you expect this issue to be completed?) - 5/17
@partapparam
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.
If you need help, be sure to either: 1) place your issue in the Questions/In Review
column of the Project Board 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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.
You are receiving this comment because your last comment was before Tuesday, May 14, 2024 at 12:06 AM PST.
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Hi Team, I need to drop this issue. I'm unable to dedicate time to complete it due to some other commitments.
Hi @t-will-gillis, 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).
Hi @t-will-gillis, 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 :)
Overview
We need to create a GitHub Action that will be triggered by GitHub
issue
,issue_comment
,pull_request
,pull_request_review
andpull_request_review_comment
events and will post comments to the developer's pre-work issue describing the developer's activities.Action Items
[ ] Become familiar with HfLA's GitHub Actions and HfLA's GitHub Actions wiki page
[ ] The following event/activity types should trigger workflows/actions:
opened
,assigned
,unassigned
,closed as completed
, orclosed as not planned
created
opened
,closed
submitted
created
[ ] Create one or more new jobs and/or actions to:
opened
issue events - the issue authorassigned
,unassigned
, andclosed
issue events- the issue assignee[ISSUE # or PR# or link to comment ] has been [ACTIVITY DESCRIPTION] by [REPLACE WITH CONTRIBUTOR GITHUB HANDLE]
[ ] Integrate the job into existing or new workflows with the appropriate triggers
[ ] Test the new GHA using your copy of the Project Board
Resources/Instructions