-
Notifications
You must be signed in to change notification settings - Fork 427
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Co-authored-by: Isak Einberg <[email protected]>
- Loading branch information
1 parent
3ad49da
commit 57b138d
Showing
1 changed file
with
30 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
# Assignment Proposal | ||
|
||
## Title | ||
|
||
Enterprise CI with Github Actions | ||
|
||
## Names and KTH ID | ||
|
||
- Hampus Hallkvist ([email protected]) | ||
- Isak Einberg ([email protected]) | ||
|
||
## Deadline | ||
|
||
- Week 2 | ||
|
||
## Category | ||
|
||
- Demo | ||
|
||
## Description | ||
|
||
We want to cover three different CI github actions during week 2. We're thinking starting from a rust project and then apply: | ||
|
||
- Unit testing integration through cargo (rust's package manager) | ||
- Correct pull request formatting (enforcing that PRs are correctly formatted, making sure there is consistency when new contributors join the project) | ||
- Pull request notification to slack (alerting the rest of the team directly through integration with communication tools) | ||
|
||
**Relevance** | ||
|
||
These are three very relevant topics for code quality and maintainability in enterprise development. We think this will give a good overview of how the workflow might look like in a real project. |