Conversation
|
Hi @mansogf, Looking at the context (contribution to a community), I realized that I made some mistakes. Sorry for that. The PR was implemented according to my previous experiences and inclinations. I forgot to ask what kind of solutions the community expected. Sorry. I would like to know:
If I forgot something, please let me know. Thanks for you attention. |
The answers are yes and yes =) . |
m-theus
force-pushed
the
2-setup-ci/cd-for-backend
branch
3 times, most recently
from
ad30cb9 to
3b74756
Compare
Fix Computer-Progress#2: Add build badge to README.md Fix Computer-Progress#2: Add pytest-cov Fix Computer-Progress#2: Add .coveragerc Fix Computer-Progress#2: Add flake8 Fix Computer-Progress#2: Add test script Fix Computer-Progress#2: Add workflow to test Fix Computer-Progress#2: Add workflow to style Fix Computer-Progress#2: Update README.md and pyproject.toml Fix Computer-Progress#2: Update README.md Fix Computer-Progress#2: Adapting solution to the target repository
m-theus
force-pushed
the
2-setup-ci/cd-for-backend
branch
from
3b74756 to
1fef69a
Compare
|
@mansogf, Changes completed. |
m-theus
force-pushed
the
2-setup-ci/cd-for-backend
branch
from
765407b to
cb83519
Compare
m-theus
force-pushed
the
2-setup-ci/cd-for-backend
branch
from
9a0aed5 to
34764b7
Compare
2 participants
Description
This PR sets up three CI/CD workflows:
Build workflow
Checks if the application build is running without errors.
Style workflow (with flake8)
Checks if the application code follows the default style.
Test workflow (with coverage)
Verifies that all application tests are passing and checks application testing coverage.
These workflows will run on every PR or push to main branch. And each workflow has a badge in the README to report its status.
Images
Badges
Related Issue
#2