Skip to content
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

Remove requirements.txt file from repository #3

Merged
merged 1 commit into from
May 28, 2023

Conversation

boomanaiden154
Copy link
Collaborator

Having this file checked into the repository means that the ignore line in .gitignore is essentially nonfunctional. This patch removes requirements.txt so that the ignore line in .gitignore is functional and the generated requirements.txt doesn't accidentally end up in any commits.

Having this file checked into the repository means that the ignore line
in .gitignore is essentially nonfunctional. This patch removes
requirements.txt so that the ignore line in .gitignore is functional and
the generated requirements.txt doesn't accidentally end up in any
commits.
@ondrasej
Copy link
Collaborator

I think I tried this and git still ignored changes made to the file, but ack. Creating the file is documented in README, so we don't really need it.

@ondrasej ondrasej merged commit 50c9589 into google:main May 28, 2023
1 check passed
boomanaiden154 added a commit to boomanaiden154/rules_python that referenced this pull request Jun 2, 2023
The documentation is currently ambiguous on whether or not to check
requirements.txt into version control. This has raised some confusion in
other projects (e.g., google/gematria#3). This
makes it clear that requirements.txt files produced by this rule should
be checked into version control in an easy to find place to avoid
confusion.
boomanaiden154 added a commit to boomanaiden154/rules_python that referenced this pull request Jun 2, 2023
The documentation is currently ambiguous on whether or not to check
requirements.txt into version control. This has raised some confusion in
other projects (e.g., google/gematria#3). This
makes it clear that requirements.txt files produced by this rule should
be checked into version control in an easy to find place to avoid
confusion.
github-merge-queue bot pushed a commit to bazelbuild/rules_python that referenced this pull request Jun 2, 2023
The documentation is currently ambiguous on whether or not to check
requirements.txt into version control. This has raised some confusion in
other projects (e.g., google/gematria#3). This
makes it clear that requirements.txt files produced by this rule should
be checked into version control in an easy to find place to avoid
confusion.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants