Dealing with a New FTC Season

🧑‍💻 DevOps: Dealing with a New FTC Season

⚠️ This is not something most people in the team will need to know. It is specifically for one member of the team to use at the start of September.

In early September each year, FIRST® will release the new version of the FTC SDK here. It will be labelled as an "official release" rather than an "offseason release". Once this new version has been released, you can follow these instructions to update our GitHub repository and organisation (you should replace [old-year] with the year of the last competition, i.e. this year, and [new-year] with the year of the next competition, i.e. next year).

1. Create a new repository within this organisation named with just the next season's year, i.e. Brighton-FTC/[new-year]. Don't auto-generate any files such as a README/LICENSE. Set the description to Our FIRST® Tech Challenge Code for the [old-year]-[new-year] season..
2. In this new repo, click on the Wiki tab, and create and save a Home page. Its content will be overwritten so doesn't matter.
3. Open a PowerShell (Windows) / Terminal Emulator (Linux/macOS) session on your computer. Type git and press Enter - it should give usage instructions indicating that git is installed.

4. # Run these in the terminal one-by-one, still replacing the [old-year] and [new-year] placeholders.
   
   # Create code repo
   git clone https://github.com/First-Tech-Challenge/FtcRobotController
   cd FtcRobotController
   git remote add brighton https://github.com/Brighton-FTC/[new-year]
   git push --force -u brighton main
   cd ..
   rm -rf FtcRobotController # This won't work on Windows; just delete the FtcRobotController folder.
   
   # Transfer wiki repo
   git clone https://github.com/Brighton-FTC/[old-year].wiki
   cd [old-year].wiki
   git remote add new https://github.com/Brighton-FTC/[new-year].wiki
   code . # Only if you have Visual Studio Code; otherwise open the cloned Wiki in an IDE.
   # Edit and save the wiki Markdown files so the hyperlinks (not the image URLs) point to the [new-year] wiki rather than the [old-year] wiki. 
   git commit -am "Make hyperlinks point to [new-year] wiki"
   git push --force -u new main
   cd ..
   rm -rf [old-year].wiki # This won't work on Windows; just delete the [old-year].wiki folder.

5. Navigate to https://github.com/Brighton-FTC/[new-year] and edit the README so it reads:

   # [old-year]-[new-year] - FIRST® Tech Challenge - Brighton Programmers
   # [🗞️ Please see the wiki for all information, links and instructions.](https://github.com/Brighton-FTC/[new-year]/wiki)

6. In the "Projects" tab of the repo, click "New project". Edit its name to be [new-year]. Take note of its URL (up to but not including views if applicable).
7. Edit Brighton-FTC's profile Markdown here so the links point to the [new-year] resources (including the project link) rather than the [old-year] ones and the text shows the correct years for the new season. Commit your changes.
8. In the settings of last season's repo, archive it. Under the "Projects" tab of the organisation, close last season's project.