-
-
Notifications
You must be signed in to change notification settings - Fork 778
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
Edits to contributors-data.js
and schedule-monthly.yml
#6193
Comments
schedule-monthly.yml
schedule-monthly.yml
schedule-monthly.yml
schedule-monthly.yml
This comment was marked as outdated.
This comment was marked as outdated.
schedule-monthly.yml
contributors-data.js
and schedule-monthly.yml
Workflow ready to be implemented. |
@t-will-gillis Under resources, it says
Is this the epic, or is there an epic that this all connects to? |
@ExperimentsInHonesty Under Resources, I removed the references to the other files and left the two that are being edited. There is not an epic that this connects to so this issue could be the epic, or I could create a separate epic if there should be one. However you think is best- My mindset was that originally this issue would address everything, but then I split off the other issues since they can be edited mostly independently from this one, and this one was already very large by itself. I was planning to release a PR for this issue once the other four are done. |
@ExperimentsInHonesty Also, if it makes a difference, I am planning to submit the PR for this one assuming you approve of the changes. |
Hi @ExperimentsInHonesty I added the |
Dependents
get-timeline.js
#6459inactive-members.json
#6460create-new-issue.js
#6396Associated Files
inactive-members.md
file #6395Overview
The current
contributors-data.js
has become unwieldly and much of its functionality can be modularized. There are also several additional edits that we can make so that these files are more compatible and exchangeable with other workflows, and there are other checks and features that should be added to the inactive members workflow as detailed following.Details/ Main Objectives
contributors-data.js
to same folder as second half of workflow so files are in same folder (ie. into/list-inactive-members/
contributors-data.js
into more discrete functionalitiesgetTimeline()
to the common/utils/
foldergetTeamMembers()
to the common/utils/
folderAction Items
Move and rename
/github-data/contributors-data.js
tolist-inactive-members/get-contributors-data.js
For the next change, refactor from the use of the
octokit
object to using the github context generated byactions/github-script
. In this way, this workflow can more readily make use of, and contribute to, the reusable utility functions in thegithub-actions/utils/
folder.At the beginning of the file, replace the Octokit object:
with:
Replace all references to
octokit
withgithub
Replace
team
withwriteTeam
, around 5 locations.Copy this file to
list-inactive-members/trim-inactive-members.js
At the main() function declaration, replace:
with:
Remove the function
getEventTimeline(issueNum)
in its entirety, and replace:with:
Move function
fetchTeamMembers()
to new fileutils/get-team-members.js
Remove all code from
removeInactiveMembers()
to end and add linemodule.exports = main
In the new
trim-inactive-members.js
:Remove the section defining dates, it is not needed here
At the
main()
function, replace with edited section:Remove
fetchContributors()
throughisEventOutdated()
Within the function
removeInactiveMembers()
, add functionality to confirm that a member to-be-removed received notification in the prior month, and remove member from 'website-merge' if needed, and finally close a removed member's "Pre-work Checklist" if open. Replace:with:
Add function to automatically close an inactive member's Pre-work:
Remove the entirety of function
shouldRemoveOrNotify()
since we are not checking whether a member is a Maintainer when determining if the member is Inactive. Replace with a new check for whether a member has recently cloned the HfLA repo, since we don't want to remove members that signed up recently:Add function that will read the json file for the previous month's data to confirm that this month's to-be-removed members received a notification the prior month:
Finally, add
module.exports = main
at endIn the
schedule-monthly.yml
file we will be usingactions/github-script@v7
, thus we do not need the steps to setup Node or install the npm dependencies. Also note that the standard HfLA token is replaced by a token with extra ADMIN privileges to allow the workflow to run correctly. Replace:with:
Remove steps to save artifact, and instead save json data to repo. Replace:
with:
Resources/Instructions
schedule-monthly.yml
contributors-data.js
The text was updated successfully, but these errors were encountered: