Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: pypa/pip
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 20.2.4
Choose a base ref
...
head repository: pypa/pip
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 21.3.1
Choose a head ref
Loading
Showing 652 changed files with 81,195 additions and 43,971 deletions.
36 changes: 0 additions & 36 deletions .azure-pipelines/jobs/package.yml

This file was deleted.

65 changes: 0 additions & 65 deletions .azure-pipelines/jobs/test-windows.yml

This file was deleted.

44 changes: 0 additions & 44 deletions .azure-pipelines/jobs/test.yml

This file was deleted.

8 changes: 0 additions & 8 deletions .azure-pipelines/linux.yml

This file was deleted.

8 changes: 0 additions & 8 deletions .azure-pipelines/macos.yml

This file was deleted.

54 changes: 0 additions & 54 deletions .azure-pipelines/steps/run-tests-windows.yml

This file was deleted.

25 changes: 0 additions & 25 deletions .azure-pipelines/steps/run-tests.yml

This file was deleted.

8 changes: 0 additions & 8 deletions .azure-pipelines/windows.yml

This file was deleted.

2 changes: 1 addition & 1 deletion .gitattributes
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Patches must have Unix-style line endings, even on Windows
tools/automation/vendoring/patches/* eol=lf
tools/vendoring/patches/* eol=lf
# The CA Bundle should always use Unix-style line endings, even on Windows
src/pip/_vendor/certifi/*.pem eol=lf
3 changes: 0 additions & 3 deletions .github/ISSUE_TEMPLATE.md

This file was deleted.

36 changes: 0 additions & 36 deletions .github/ISSUE_TEMPLATE/bug-report.md

This file was deleted.

79 changes: 79 additions & 0 deletions .github/ISSUE_TEMPLATE/bug-report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,79 @@
name: Bug report
description: Something is not working correctly.
labels: "S: needs triage, type: bug"

body:
- type: markdown
attributes:
value: >-
Hi there!
We'd appreciate it if you could search on pip's existing issues prior to filing
a bug report.
We get a lot of duplicate tickets and have limited maintainer capacity to triage
them. Thanks!
- type: textarea
attributes:
label: Description
description: >-
A clear and concise description of what the bug is.
validations:
required: true

- type: textarea
attributes:
label: Expected behavior
description: >-
A clear and concise description of what you expected to happen.
- type: input
attributes:
label: pip version
validations:
required: true
- type: input
attributes:
label: Python version
validations:
required: true
- type: input
attributes:
label: OS
validations:
required: true

- type: textarea
attributes:
label: How to Reproduce
description: Please provide steps to reproduce this bug.
placeholder: |
1. Get package from '...'
2. Then run '...'
3. An error occurs.
validations:
required: true

- type: textarea
attributes:
label: Output
description: >-
Provide the output of the steps above, including the commands
themselves and pip's output/traceback etc. If you're familiar with
Markdown, this block will have triple backticks added automatically
around it -- you don't have to add them.
If you want to present output from multiple commands, please present
that as a shell session (commands you run get prefixed with `$ `).
Please also ensure that the "How to reproduce" section contains matching
instructions for reproducing this.
render: sh-session

- type: checkboxes
attributes:
label: Code of Conduct
options:
- label: >-
I agree to follow the [PSF Code of Conduct](https://www.python.org/psf/conduct/).
required: true
Loading