-
Notifications
You must be signed in to change notification settings - Fork 0
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add CI config for project template #12
Comments
Merged
zahraaalizadeh
added a commit
that referenced
this issue
Apr 5, 2024
This change: - Fixes a few typos - Adds a basic CI configuration to run `format` task on the subproject - Adds a documentation about how to use 'act' to run github workflows locally. - Updates the README file with how to include github workflows when starting a new project. issue: #12
This was referenced Apr 5, 2024
Merged
zahraaalizadeh
added a commit
that referenced
this issue
Apr 10, 2024
This change adds the following CI configs: - Linting - Type checking - Doc building issue: #12
zahraaalizadeh
added a commit
that referenced
this issue
Apr 15, 2024
This PR adds run-test job to the CI pipeline. It also introduces a new invoke task to install dependencies to make the setup operations clean and minimal. Issue: #12
zahraaalizadeh
added a commit
that referenced
this issue
Apr 24, 2024
This change adds the last piece required in #12 Adds: - An invoke task to run the service Docker image - A CI job to build and test the docker image
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃幆 Aim
Add basic CI configuration for the project template.
馃摃Context
The template project currently has no CI (Continuous Integration) runner configuration but should have at least support for running tests, static analysis, building docs and the docker image. This will help ensure that projects are set up with good development practices right for the start.
I (@a-musing-moose) have a strong preference that CI jobs should not only be possible in the CI runner - it should be possible to run them all locally as well. This ensures that CI failures are resolvable offline, and that we are not 100% dependant on the CI runner to get anything done. As such the CI jobs should mostly be wrappers around existing Invoke task.
馃摑 Relevant resources/doc's/people
鉁匒cceptance Criteria
The text was updated successfully, but these errors were encountered: