UBCSailbot / tasks

Repository to track tasks not related to any of our GitHub repositories
0 stars 0 forks source link

Figure out subteam repository CI #22

Closed patrick-5546 closed 1 year ago

patrick-5546 commented 2 years ago

Purpose

Doesn't really make sense for CI to be run in sailbot_workspace, should be in the subteams' repositories.

Changes

Can explore this in network_systems, the only new project subteam repo created so far. I'm thinking that we can move the lint and test CI from sailbot_workspace to network_systems. One complexity will be using the .devcontainer/Dockerfile image in sailbot_workspace. Then we can create a starter workflow from what we learned so that it will be easy to add CI in future subteam repositories.

To Do

Resources

patrick-5546 commented 2 years ago

@hhenry01 If you want to start development on network_systems this would be a good issue to address first

hhenry01 commented 1 year ago

Resolved when these two PRs are merged: https://github.com/UBCSailbot/network_systems/pull/6, https://github.com/UBCSailbot/sailbot_workspace/pull/60

How it was done

Part 1: Network Systems Repo

Questions

  1. I'm not sure what the dependabot.yml and release.yml file found under .github/ do, so I left them in both.
patrick-5546 commented 1 year ago

I'm not sure what the dependabot.yml and release.yml file found under .github/ do, so I left them in both.