-
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
open an issue automatically when a PR is merged on google/transit #1080
Comments
There is an interesting thread here: https://github.com/orgs/community/discussions/26323 |
The logic would be: if REFERENCE.md is modified, we open an issue. |
Implemented! Waiting for next merge on reference.md to google/transit to test. It's on me to check this and mark this "done". Will likely take a few months for the next spec vote. cc @jcpitre @fredericsimard |
Guessing it didn't work? |
@isabelle-dr No, it did. Here's an example: #1601 |
@fredericsimard @isabelle-dr Finally confirmed success from #1601, so closing now. |
@fredericsimard Reopening for one more request with this: can we automatically add the "needs triage" label to any issue that comes from this workflow? |
Certainly. See here: #1610 |
In order to keep the validator up to date with the changes, we need to review PR's merged on the official specification to see if we need to modify a rule in the Canonical GTFS Schedule Validator.
Having an automatic issue would help to make sure we don't miss anything.
Additional context in:
The text was updated successfully, but these errors were encountered: