Closed NickWalt01 closed 1 year ago
Emailed these users to log into MoJ GH Org before Mid June
re-start ticket after 19th June
Emailed these users on the AS Org to log in before start the process in June
Update the Allow list AS Org: adchester gilad-ravitz joggers7
used Notify to send the reminder email to the MoJ Org and AS Org users who were inactive last month
AS allow list updated
removed 17 users from the MoJ GH Org as part of inactive users process, usernames are in the CI trace for when a user ask to be re-invited to the Org and sent those users an email via Notify to tell them we did removed them
I’ve removed 54 users from the AS GH Org as part of inactive users process, usernames are in the CI trace for when a user ask to be re-invited to the Org. Notify has emailed those users that we have removed them as well. We now have 84 spare GH seats.
Background
Remove the inactive users from the GH Org MoJ and AS.
Proposed user journey
Run the Dormant GH Users scripts on the MoJ and AP GH Orgs, get the dormant export file from Tony, add it to the repo, run the script with false, email all the users that are not active, after a week or two, get another Dormant export file from Tony, run the script with false to check for any new users, add new users usernames to the allow list within the script file temporarily on a branch, run the script with true against the branch, to remove the users that haven't logged into GH, run the the script with false on the main branch, get the list of users and email them to log in before the next date run this process.
expect users to email / slack us after being removed to be added back into the GH Orgs.
Before removing users post a heads up in the slack channels for AS, Data Engineering, and our channels so that users are aware that we will be removing users soon