mirror of
https://github.com/FIRST-Tech-Challenge/scorekeeper.git
synced 2026-03-09 21:56:44 -04:00
Compare commits
11 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
129df321dc | ||
|
|
a61d5d3443 | ||
|
|
3c18627718 | ||
|
|
929169b123 | ||
|
|
aa5d6e957c | ||
|
|
ed84e31ec9 | ||
|
|
d58704fb79 | ||
|
|
ef81371fea | ||
|
|
6b07906ded | ||
|
|
fd56dce06b | ||
|
|
9922ab52b1 |
33
.github/ISSUE_TEMPLATE/cloud-scoring-bug-report.md
vendored
Normal file
33
.github/ISSUE_TEMPLATE/cloud-scoring-bug-report.md
vendored
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: Cloud Scoring Bug Report
|
||||
about: Submit a bug in ftc-scoring.firstinspires.org
|
||||
title: ''
|
||||
labels: Cloud, bug
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
<!--- DO NOT INCLUDE PRIVATE INFORMATION IN THIS ISSUE --->
|
||||
|
||||
**Describe the bug**
|
||||
A clear and concise description of what the bug is.
|
||||
|
||||
**To Reproduce**
|
||||
Steps to reproduce the behavior:
|
||||
1. Go to '...'
|
||||
2. Click on '....'
|
||||
3. Scroll down to '....'
|
||||
4. See error
|
||||
|
||||
**Expected behavior**
|
||||
A clear and concise description of what you expected to happen.
|
||||
|
||||
**Screenshots**
|
||||
If applicable, add screenshots to help explain your problem.
|
||||
|
||||
**Device (please complete the following information):**
|
||||
- OS: [e.g. iOS]
|
||||
- Browser [e.g. chrome, safari]
|
||||
- Version [e.g. 22]
|
||||
|
||||
**Additional context**
|
||||
Add any other context about the problem here.
|
||||
20
.github/ISSUE_TEMPLATE/cloud-scoring-feature-request.md
vendored
Normal file
20
.github/ISSUE_TEMPLATE/cloud-scoring-feature-request.md
vendored
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: Cloud Scoring Feature Request
|
||||
about: Suggest an idea for for ftc-scoring.firstinspires.org
|
||||
title: ''
|
||||
labels: Cloud, enhancement
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
**Is your feature request related to a problem? Please describe.**
|
||||
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
|
||||
|
||||
**Describe the solution you'd like**
|
||||
A clear and concise description of what you want to happen.
|
||||
|
||||
**Describe alternatives you've considered**
|
||||
A clear and concise description of any alternative solutions or features you've considered.
|
||||
|
||||
**Additional context**
|
||||
Add any other context or screenshots about the feature request here.
|
||||
1
.github/ISSUE_TEMPLATE/config.yml
vendored
Normal file
1
.github/ISSUE_TEMPLATE/config.yml
vendored
Normal file
@@ -0,0 +1 @@
|
||||
blank_issues_enabled: false
|
||||
16
.github/ISSUE_TEMPLATE/documentation-request.md
vendored
Normal file
16
.github/ISSUE_TEMPLATE/documentation-request.md
vendored
Normal file
@@ -0,0 +1,16 @@
|
||||
---
|
||||
name: Documentation Update Request
|
||||
about: Request an addition, correction or update to documentation
|
||||
title: ''
|
||||
labels: documentation
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
** Requested Change **
|
||||
What you would like to see updated (or added) to documentation
|
||||
|
||||
** Relevant existing documentation **
|
||||
A link to any existing documentation, with page number if appropriate
|
||||
|
||||
|
||||
33
.github/ISSUE_TEMPLATE/ftc-events-bug-report.md
vendored
Normal file
33
.github/ISSUE_TEMPLATE/ftc-events-bug-report.md
vendored
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: FTC Events Bug Report
|
||||
about: Submit a bug in ftc-events.firstinspires.org (including ftc-api)
|
||||
title: ''
|
||||
labels: ftc-events, bug
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
<!--- DO NOT INCLUDE PRIVATE INFORMATION IN THIS ISSUE --->
|
||||
|
||||
**Describe the bug**
|
||||
A clear and concise description of what the bug is.
|
||||
|
||||
**To Reproduce**
|
||||
Steps to reproduce the behavior:
|
||||
1. Go to '...'
|
||||
2. Click on '....'
|
||||
3. Scroll down to '....'
|
||||
4. See error
|
||||
|
||||
**Expected behavior**
|
||||
A clear and concise description of what you expected to happen.
|
||||
|
||||
**Screenshots**
|
||||
If applicable, add screenshots to help explain your problem.
|
||||
|
||||
**Device (please complete the following information):**
|
||||
- OS: [e.g. iOS]
|
||||
- Browser [e.g. chrome, safari]
|
||||
- Version [e.g. 22]
|
||||
|
||||
**Additional context**
|
||||
Add any other context about the problem here.
|
||||
20
.github/ISSUE_TEMPLATE/ftc-events-feature-request.md
vendored
Normal file
20
.github/ISSUE_TEMPLATE/ftc-events-feature-request.md
vendored
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: FTC Events Feature Request
|
||||
about: Suggest an idea for for ftc-events.firstinspires.org (including ftc-api)
|
||||
title: ''
|
||||
labels: ftc-events, enhancement
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
**Is your feature request related to a problem? Please describe.**
|
||||
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
|
||||
|
||||
**Describe the solution you'd like**
|
||||
A clear and concise description of what you want to happen.
|
||||
|
||||
**Describe alternatives you've considered**
|
||||
A clear and concise description of any alternative solutions or features you've considered.
|
||||
|
||||
**Additional context**
|
||||
Add any other context or screenshots about the feature request here.
|
||||
33
.github/ISSUE_TEMPLATE/local--ftclive--bug-report.md
vendored
Normal file
33
.github/ISSUE_TEMPLATE/local--ftclive--bug-report.md
vendored
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: Traditional (FTCLive) Bug Report
|
||||
about: Submit a bug in the traditional scoring system
|
||||
title: ''
|
||||
labels: Local, bug
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
<!--- DO NOT INCLUDE PRIVATE INFORMATION IN THIS ISSUE --->
|
||||
|
||||
**Describe the bug**
|
||||
A clear and concise description of what the bug is.
|
||||
|
||||
**To Reproduce**
|
||||
Steps to reproduce the behavior:
|
||||
1. Go to '...'
|
||||
2. Click on '....'
|
||||
3. Scroll down to '....'
|
||||
4. See error
|
||||
|
||||
**Expected behavior**
|
||||
A clear and concise description of what you expected to happen.
|
||||
|
||||
**Screenshots**
|
||||
If applicable, add screenshots to help explain your problem.
|
||||
|
||||
**Device (please complete the following information):**
|
||||
- OS: [e.g. iOS]
|
||||
- Browser [e.g. chrome, safari]
|
||||
- Version [e.g. 22]
|
||||
|
||||
**Additional context**
|
||||
Add any other context about the problem here.
|
||||
20
.github/ISSUE_TEMPLATE/local--ftclive--feature-request.md
vendored
Normal file
20
.github/ISSUE_TEMPLATE/local--ftclive--feature-request.md
vendored
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: Traditional (FTCLive) Feature Request
|
||||
about: Suggest an idea for the traditional scoring system
|
||||
title: ''
|
||||
labels: Local, enhancement
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
**Is your feature request related to a problem? Please describe.**
|
||||
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
|
||||
|
||||
**Describe the solution you'd like**
|
||||
A clear and concise description of what you want to happen.
|
||||
|
||||
**Describe alternatives you've considered**
|
||||
A clear and concise description of any alternative solutions or features you've considered.
|
||||
|
||||
**Additional context**
|
||||
Add any other context or screenshots about the feature request here.
|
||||
14
README.md
14
README.md
@@ -1,4 +1,14 @@
|
||||
# Welcome!
|
||||
# Attention: Remote Events
|
||||
|
||||
This is the software used to run **traditional** in-person events.
|
||||
|
||||
If you are a mentor or team administrator trying to score **remote** event matches, go here: [FTC Remote Scoring](https://ftc-scoring.firstinspires.org)
|
||||
|
||||
Full documentation can be found in the [FTC Scoring Team Guide](https://www.firstinspires.org/sites/default/files/uploads/resource_library/ftc/scoring-team-guide.pdf)
|
||||
|
||||
A video walkthrough can be found on YouTube: [Remote Event Scoring For Teams](https://www.youtube.com/watch?v=5pGDi_Kq7ks&list=PLEuGrYl8iBm48sXHM8wOIPECDvD1zGgr2)
|
||||
|
||||
# Welcome: Traditional Events
|
||||
This GitHub repository can be used to download the _FIRST_ Tech Challenge Live scorekeeper software. Also, if you have a GitHub user account, you can use the ["Issues" database](https://github.com/FIRST-Tech-Challenge/scorekeeper/issues) to report and track issues with the software.
|
||||
|
||||
## Downloading the software
|
||||
@@ -17,7 +27,7 @@ Note that you want to download the "FIRST-Tech-Challenge-Live" archive file, and
|
||||
## Documentation
|
||||
The user documentation can be found here:
|
||||
|
||||
[FTC Scorekeeper Manual](https://github.com/FIRST-Tech-Challenge/scorekeeper/files/2563026/FTC.Scorekeeper.Manual.v0.5.1.1.pdf)
|
||||
[FTC Scorekeeper Manual](https://firstinspiresst01.blob.core.windows.net/first-energize-ftc/scorekeeper-guide.pdf)
|
||||
|
||||
## Reporting Issues
|
||||
Click on the ["Issues" link](https://github.com/FIRST-Tech-Challenge/scorekeeper/issues) towards the upper left hand corner of the main page of this repository to navigate to the [Issue Tracking Database page](https://github.com/FIRST-Tech-Challenge/scorekeeper/issues). If you are logged in to your GitHub user account (which is available for free from GitHub) you can create and reply to issues in the database.
|
||||
|
||||
Reference in New Issue
Block a user