Merged
Conversation
github-actions
Bot
removed
the
development-process
Contributor
Author
|
If someone needs additional lines in .gitignore to help their workflow I think we should definitely merge them in -- there is no harm in having more stuff in here. |
Contributor
Author
|
Thanks @comphead |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #.
Rationale for this change
While working on #12034 I noticed a bunch of stuff in .gitignore that was left over from when this code was pulled from the arrow monorepo: https://github.com/apache/arrow/blob/main/.gitignore
What changes are included in this PR?
Remove the obviously irrelevant parts of .gitignore
I am sure there is more we could remove but this is an improvement already in my mind
Are these changes tested?
Sort of by CI
Are there any user-facing changes?
No, this is entirely development process changes