Skip to content
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

2023-11-17 — 1 new commit(s) made to reference.md in Google Transit's repo #1601

Closed
mobilitydataio opened this issue Nov 17, 2023 · 3 comments · Fixed by #1609
Closed

2023-11-17 — 1 new commit(s) made to reference.md in Google Transit's repo #1601

mobilitydataio opened this issue Nov 17, 2023 · 3 comments · Fixed by #1609
Assignees
Labels
status: Needs triage Applied to all new issues

Comments

@mobilitydataio
Copy link

Commit Nº 1

AUTHOR × DATE

  • Sergio Delgado Rodriguez ( Sergiodero )
  • November 16, 2023 @ 03:06 PM ETC (08:06 PM UTC)

MESSAGE

Best practices: adding Dataset Publishing guidelines and Practice Recommendations for all files (#406)
* BP merge second iteration 
Incorporating the following Best Practices into the GTFS Reference document:
- Dataset Publishing & General Practice guidelines
- Practice Recommendations for all files
* BP merge second iteration update
Moving Dataset Publishing & General Practice guidelines before Field Definitions section.
Merging File Recommendations with File Requirements section.
* Update revision date in reference.md
Updated revision date to Nov 16, 2023

FILES CHANGED

google/transit@8268169

https://github.com/google/transit/commit/8268169a5f565e47ab9f965366ce44bd42959f2e

Copy link

welcome bot commented Nov 17, 2023

Thanks for opening your first issue in this project! If you haven't already, you can join our slack and join the #gtfs-validators channel to meet our awesome community. Come say hi 👋!

Welcome to the community and thank you for your engagement in open source! 🎉

@isabelle-dr
Copy link
Contributor

Wow!

Would be even better if the label "Needs triage" was automatically applied 😄

@emmambd
Copy link
Contributor

emmambd commented Nov 25, 2023

In the case of this PR, we already have two notices for these spec recommendations:

The GTFS validator documentation References section should be updated to point to the GTFS Schedule reference file now instead of Best Practices.
Screenshot 2023-11-25 at 10 59 46 AM

emmambd added a commit that referenced this issue Nov 28, 2023
…1609)

* Update MixedCaseRecommendedFieldNotice.java

* Update SectionRefLink.svelte

* Update ExpiredCalendarValidator.java

* format fix

---------

Co-authored-by: David Gamez <1192523+davidgamez@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: Needs triage Applied to all new issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants