Skip to content

Conversation

@giocorti
Copy link

@giocorti giocorti commented May 29, 2019

This is one of 5 PRs that incorporates a recommendation from the GTFS best practices.

This PR adds examples detailing proper headsign and route name conventions

The 4 related PRs can are:

@giocorti giocorti changed the title Add best practices: Headsign and route name examples Add best practice: Headsign and route name examples Jun 3, 2019
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


giocorti seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Feb 13, 2022
@github-actions
Copy link

This pull request has been closed due to inactivity. Pull requests can always be reopened after they have been closed. See the Specification Amendment Process.

@github-actions github-actions bot closed this Feb 20, 2022
@e-lo
Copy link

e-lo commented Mar 8, 2022

This should probably be moved to mobilitydata/gtfs-ba?

cc: @scmcca

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants