fix: add repo health job workflow

[UsamaSadiq]

Description

• Fixes the issue Move repo health job from Jenkins to GHA edx/edx-arch-experiments#66
• Added a reusable workflow to run the repo health job on given organisation's repos.
• Added template workflow for organisations to trigger & use the repo-health-job reusable workflow.
• Some constraints will be removed after completing the testing on the PR.

Testing

• Reusable workflow has been tested in the fork both ways:

1. By being triggered from a workflow under same organisation
2. By being triggered from a workflow under different organisation

[UsamaSadiq]

@nedbat @jmbowman
I tried re-requesting review from both of you but for some reason, GitHub wants me to only ask for review from one person at a time 😅 and removes other one automatically.

[nedbat]

Thanks for taking care of my earlier concerns. The repo-health-script.sh file is long for a shell script. I feel better about it if it was more uniform: I counted at least four different styles of if-statements and indentation.

[UsamaSadiq]

Hi @nedbat as per Jeremy's suggestion, I'll be moving the repo-health-job.yml script into the edx-repo-health repo so we won't have to clone it seperately to execute in the workflow.
I'll address your concerns about the shell script in the edx-repo-health PR to add the shell script. Most of these points were also noticed by our team before creating this PR but since this script was already being used in Jenkins like this, we wanted to do the minimal chansges in the script to make it work with our workflows.

[nedbat]

Hi @nedbat as per Jeremy's suggestion, I'll be moving the repo-health-job.yml script into the edx-repo-health repo so we won't have to clone it seperately to execute in the workflow.
I'll address your concerns about the shell script in the edx-repo-health PR to add the shell script. Most of these points were also noticed by our team before creating this PR but since this script was already being used in Jenkins like this, we wanted to do the minimal chansges in the script to make it work with our workflows.

I guess you mean those changes will be in a new pull request? Then let's go ahead with this one.

[jmbowman]

Looks good to me once the linked PR is merged.

[UsamaSadiq]

@jmbowman
Could you merge this PR if you have merge access in the repo? or should I create a tcril issue for this to get this PR merged?

After this PR is merged:

• A PR will be created to create the trigger workflow in the 2U org which will use this reusable workflow to populate the existing google sheet.
• An SRE ticket will be created to copy the existing credentials from Jenkins env to edx org secrets which will be used by the workflow.
• An announcement will be made for the open edx community to inform about this tool and list down the steps needed for the other orgs to be able to use this for their reops.

Question: Which will be the best place in the edx org to host the trigger workflow for repo health job? edx/.github or repo-tools?

[jmbowman]

I don't have merge rights, so that'll need to be a tCRIL issue. And I'd suggest edx/repo-health-data for the 2U version of the job, to avoid leaking information about private repositories in public workflow logs.