Conda 23.3.x Documentationways: 1. it helps you by automating the nitpicky process of identifying and correcting code style/quality issues 2. it helps us where during code review we can focus on the substance of your contribution ticket triage. • Add and automatically run pre-commit as part of the CI system to improve the code quality continuously and raise issues in contributed patches early on. The used code linters are: flake80 码力 | 370 页 | 2.94 MB | 8 月前3- Conda 23.5.x Documentationways: 1. it helps you by automating the nitpicky process of identifying and correcting code style/quality issues 2. it helps us where during code review we can focus on the substance of your contribution ticket triage. • Add and automatically run pre-commit as part of the CI system to improve the code quality continuously and raise issues in contributed patches early on. The used code linters are: flake80 码力 | 370 页 | 3.11 MB | 8 月前3
- Conda 23.10.x Documentationticket triage. • Add and automatically run pre-commit as part of the CI system to improve the code quality continuously and raise issues in contributed patches early on. The used code linters are: flake8 ways: 1. it helps you by automating the nitpicky process of identifying and correcting code style/quality issues 2. it helps us where during code review we can focus on the substance of your contribution0 码力 | 773 页 | 5.05 MB | 8 月前3
- Conda 23.7.x Documentationways: 1. it helps you by automating the nitpicky process of identifying and correcting code style/quality issues 2. it helps us where during code review we can focus on the substance of your contribution ticket triage. • Add and automatically run pre-commit as part of the CI system to improve the code quality continuously and raise issues in contributed patches early on. The used code linters are: flake80 码力 | 795 页 | 4.91 MB | 8 月前3
- Conda 23.11.x Documentationticket triage. • Add and automatically run pre-commit as part of the CI system to improve the code quality continuously and raise issues in contributed patches early on. The used code linters are: flake8 ways: 1. it helps you by automating the nitpicky process of identifying and correcting code style/quality issues 2. it helps us where during code review we can focus on the substance of your contribution0 码力 | 781 页 | 4.79 MB | 8 月前3
- Conda 24.1.x Documentationticket triage. • Add and automatically run pre-commit as part of the CI system to improve the code quality continuously and raise issues in contributed patches early on. The used code linters are: flake8 ways: 1. it helps you by automating the nitpicky process of identifying and correcting code style/quality issues 2. it helps us where during code review we can focus on the substance of your contribution0 码力 | 795 页 | 4.73 MB | 8 月前3
- Conda 24.3.x Documentationticket triage. • Add and automatically run pre-commit as part of the CI system to improve the code quality continuously and raise issues in contributed patches early on. The used code linters are: flake8 ways: 1. it helps you by automating the nitpicky process of identifying and correcting code style/quality issues 2. it helps us where during code review we can focus on the substance of your contribution0 码力 | 786 页 | 4.98 MB | 8 月前3
- Conda 24.4.x Documentationticket triage. • Add and automatically run pre-commit as part of the CI system to improve the code quality continuously and raise issues in contributed patches early on. The used code linters are: flake8 ways: 1. it helps you by automating the nitpicky process of identifying and correcting code style/quality issues 2. it helps us where during code review we can focus on the substance of your contribution0 码力 | 786 页 | 4.99 MB | 8 月前3
- Conda 24.5.x Documentationticket triage. • Add and automatically run pre-commit as part of the CI system to improve the code quality continuously and raise issues in contributed patches early on. The used code linters are: flake8 ways: 1. it helps you by automating the nitpicky process of identifying and correcting code style/quality issues 2. it helps us where during code review we can focus on the substance of your contribution0 码力 | 794 页 | 5.01 MB | 8 月前3
- Conda 25.1.x Documentationticket triage. • Add and automatically run pre-commit as part of the CI system to improve the code quality continuously and raise issues in contributed patches early on. The used code linters are: flake8 ways: 1. it helps you by automating the nitpicky process of identifying and correcting code style/quality issues 2. it helps us where during code review we can focus on the substance of your contribution0 码力 | 822 页 | 5.20 MB | 8 月前3
共 14 条
- 1
- 2