Merged
Conversation
…en simpele test voor backend.
…en simpele test voor backend.
…Dwengo-2 into 10-github-actions-setup
…hanges to dockerfile so it will install chromium.
Closed
Contributor
|
Perhaps it would be wiser to also add testing requirements on each branch we try to merge into another? That way, we only work with code that is guaranteed to work. |
Contributor
Author
|
The actions will now execute on every branch, I also made some changes to the rights on the server that caused the first commit to not be accepted. |
bramcomyn
approved these changes
Feb 26, 2025
thomasdejaeghere
approved these changes
Feb 26, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implementation of a CI (continuous integration) using github actions via a self-hosted runner.
The CI will execute the github actions and will lint and test the code upon a pull request/push, on the main/development branch.
Simple tests and configurations were used, but can be changed in the future to further integrate more detailed checks.
Deployment will be added later because right now I want to make sure that the testing and linting actions work correctly, and are able to run on our self-hosted runner (locally you can only test your Github actions on the Github runners).