Skip to content

Migrate copyrite configuration #5948

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 21, 2022
Merged

Conversation

Pierre-Sassoulas
Copy link
Member

Type of Changes

Type
βœ“ πŸ› Bug fix
βœ“ ✨ New feature
βœ“ πŸ”¨ Refactoring
βœ“ πŸ“œ Docs

Description

First step toward #5877. Done independently so we can see what really changed in the configuration later.

@Pierre-Sassoulas Pierre-Sassoulas added the Maintenance Discussion or action around maintaining pylint or the dev workflow label Mar 21, 2022
@Pierre-Sassoulas Pierre-Sassoulas added this to the 2.13.0 milestone Mar 21, 2022
@Pierre-Sassoulas Pierre-Sassoulas merged commit 5a4a720 into main Mar 21, 2022
@Pierre-Sassoulas Pierre-Sassoulas deleted the migrate-copyrite-configuration branch March 21, 2022 17:01
@DanielNoord
Copy link
Collaborator

@Pierre-Sassoulas I see you've gotten some time again.

Just wondering, is there anything keeping us from releasing 2.13 as is? With the removal of Python 3.6 and the line of PRs waiting I think we release 2.14 relatively soon afterwards. There don't seem to be any crucial PRs (for end-users anyway) open right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Discussion or action around maintaining pylint or the dev workflow
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants