The automation itself I do in pypyr pipelines, which allows me to run the same CI/CD sequences locally as on the CI/CD server itself. This helps a lot with simplifying troubleshooting the devops itself.
So a single command runs the build/test/deploy sequence locally, and you can run the same single command on the GitHub Actions for the same effect.
Because the real work happens in the pypyr automation pipeline, this means you can jump between CI/CD hosts without a fuss, because they're really just providing the execution environment.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
GitHub Actions to host the CI/CD process.
The automation itself I do in pypyr pipelines, which allows me to run the same CI/CD sequences locally as on the CI/CD server itself. This helps a lot with simplifying troubleshooting the devops itself.
So a single command runs the build/test/deploy sequence locally, and you can run the same single command on the GitHub Actions for the same effect.
Because the real work happens in the pypyr automation pipeline, this means you can jump between CI/CD hosts without a fuss, because they're really just providing the execution environment.