- Notifications
You must be signed in to change notification settings - Fork675
ci(gitlab-ci): create 'codestyle' job for GitLab CI/CD and local usage#3266
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Signed-off-by: Adrian DC <radian.dc@gmail.com>
nejch commentedOct 17, 2025
Hey@AdrianDC thanks for the PR. Since this doesn't normally run here (it would only normally run in our GitLab mirror athttps://gitlab.com/python-gitlab/python-gitlab where we run Docker image deploys), maybe instead we should address the root cause: is there a specific reason you need to maintain a long-living fork, other than delays in getting PRs merged upstream here? |
Changes
Documentation and testing
Please consider whether this PR needs documentation and tests.This is not required, but highly appreciated:
Thought about it due tofeat(users): implement 'skip_confirmation' in users 'emails' creation #3265,
where I ran the codestyle documented functions from an Alpine container,
but took a different approach here to match 100% the GitHub workflow (for seamless maintenance reasons),
meant for GitLab CI/CD forks / rehostes, and if interested for local usage (gcil)
PR denial is OK, will probably keep it on my fork anyways for future patch PR checks