ci(gitlab-ci): create 'codestyle' job for GitLab CI/CD and local usage by AdrianDC · Pull Request #3266 · python-gitlab/python-gitlab

Changes

• Create 'codestyle' job for GitLab CI/CD and local usage

Documentation and testing

Please consider whether this PR needs documentation and tests. This is not required, but highly appreciated:

• Documentation in the matching docs section
• Unit tests and/or functional tests

• Thought about it due to feat(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

Hey @AdrianDC thanks for the PR. Since this doesn't normally run here (it would only normally run in our GitLab mirror at https://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?

Hey !

The goal was for potential GitLab forks to run, but mostly to use gcil for easy and containerized tests every time I upstream fixes here 😉 .

Thanks for your concern !