Developers

Developers, Developers, Developers

Developers can get involved in the BikeTag project by forking any of the Open-Source BikeTag repositories and sending Pull Requests to origin repositories for updates. Look for the "help-wanted" or "good-first-issue" tags or head to the discussions of the project to see where you can contribute.

The BikeTag Project welcomes anyone and everyone to get involved and make this thing better and better. It is the expectation of the BikeTag Project and BikeTag community members that everyone, developers included, follow the BikeTag Code of Conduct which can be found in each of the BikeTag repositories.

You should be able to clone this code and get it up and running for a read-only version of the BikeTag game on your machine. See the README for more details.

GitFlow

For the new Netilfy platform based server(less) infrastructure, we will have the following breakdown of environments:

Production branch: production site: https://biketag.org API: https://api.biketag.org

Staging branch: staging site: https://biketag.io API: https://api.biketag.io

Development branch: develop site: https://biketag.dev API: https://api.biketag.dev

Local branch: [feature/your-feature-branch] site: http://locahost:8080 API: http://localhost:7200

Admin code: https://github.com/keneucker/biketag-app site: https://biketag.net API: https://api.biketag.net

This will accommodate a CI integration with both GitHub actions as well as Netlify integrated deploys. Contributors will follow the development path of the prescribed GitFlow:

1. Fork it (to your git repo)

2. Branch it (for your feature/fix)

3. Pull it (pull the target branch back into your branch before committing)

4. Commit it (your branch to your repo)

5. Push it (to your git repo)

6. PRR it (your git repo target branch to origin repo develop)*

7. PR oF fit (continue that process as necessary feedback is addressed)+

8. MoRR (PR's to develop branch are deployed to biketag.net)*

9. Merge it (develop branch is deployed to biketag.io after merged PR)

10. Watch it (develop branch is merged into production and then deployed to biketag.org)

(* = additional review phase) (+ = final fix phase)