-
Notifications
You must be signed in to change notification settings - Fork 101
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
Welcome bot and Bug triage workflows aren't working #1298
Comments
Hello @isabelle-dr, for the triage, it looks like a column has been deleted from the repository. To fix, you should map to the new column (Triage?) For the welcolme bot, I am not sure you could try and check the permissions as detailed here 😃 I was just passing by to check on how my baby gtfs-validator is doing. Looks like he's been growing a lot! v4 already!! They grow up so fast! Keep up the good work 💪🏾 ... GIF of the day ⬇️ |
Oh hey there @lionel-nj, Your baby is doing pretty well 🐥. |
About bug triage, the external Github action we are using (alex-page/github-project-automation-plus) does not work with the new types of projects in Github. Apparently they have the classic version of projects, that works with the external action we use and the V2 version, that is now the default, for which the action does not work. See alex-page/github-project-automation-plus#81 (comment) One workaround would be to create the bug triage project asa classic project. But it's possible only if we already have a classic project. I guess Github want to get rid of classic projects ASAP. |
Turns out we can create classic projects, but only at the organization level right now. Tried with one and I could not retrieve it with the Github GraphQL API, meaning it's unlikely that the bug triage action will work. I think the project needs to be at the repo level. |
I found this, could it be why the welcome bot doesn't fire?
|
I've made tiny changes to the bug triage workflow, we'll see when it is triggered next if it works. https://github.com/MobilityData/gtfs-validator/blob/master/.github/workflows/triage.yml |
Bug triage is fixed. Turns out there is no need to create an action, the new Projects have Workflows you can use to do certain actions based on conditions. I've set two workflows:
Tada!! I've disabled the Bug triage action, we could remove the YAML entirely if this works. @jcpitre Turns out you were 100% correct, the action doesn't work with the new Projects, because you don't need an action to accomplish this. :-) More info on workflows |
Describe the bug
We have a bug triage workflow that should run every time a new issue is open with a bug label. It sends a message and adds the issue to the Bug triage board.
We have a welcome bot that sends an automatic message when:
The welcome bot is configured in https://github.com/MobilityData/gtfs-validator/blob/master/.github/config.yml
The bug triage is configured in https://github.com/MobilityData/gtfs-validator/blob/master/.github/workflows/triage.yml
It looks like they aren't working anymore.
Steps/Code to Reproduce
The welcome bot didn't run when this PR was opened by a first-time contributor.
The bug triage didn't run when this issue was open.
Expected Results
The workflows run.
See this issue where both workflows ran in August.
Actual Results
nothing
Screenshots
No response
Files used
No response
Validator version
4.0.0
Operating system
MacOS
Java version
No response
Additional notes
No response
The text was updated successfully, but these errors were encountered: