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

Use correct TBA key for backup robots #23

Closed
wants to merge 1 commit into from
Closed

Use correct TBA key for backup robots #23

wants to merge 1 commit into from

Conversation

ograff
Copy link
Contributor

@ograff ograff commented Oct 3, 2016

TBA expects keys like "1234B" for backup robots, and has no way to
distinguish that "9234" is the backup bot for "1234" aside from being
manually told. Use the approriate team key when pushing to TBA.

TBA expects keys like "1234B" for backup robots, and has no way to
distinguish that "9234" is the backup bot for "1234" aside from being
manually told. Use the approriate team key when pushing to TBA.
@fangeugene
Copy link
Contributor

We should make sure this plays well with the TBA trusted API before this is merged.

@ograff
Copy link
Contributor Author

ograff commented Oct 3, 2016

I emailed @gregmarra asking about that but have not heard back. I did spin up a local test instance of TBA and pointed Cheesy-arena at that and it worked fine, showing the backup teams properly.

@fangeugene
Copy link
Contributor

Actually, this will need the-blue-alliance/the-blue-alliance#1638

@fangeugene
Copy link
Contributor

This should make use of #56 once it gets implemented.

@ograff
Copy link
Contributor Author

ograff commented Apr 18, 2018

Closing due to inactivity.

@ograff ograff closed this Apr 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants