MINOR: [R] Fix .lintr config file for updated lintr dependency #38639
Conversation
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
|
After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 3d96bab. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 3 possible false positives for unstable benchmarks that are known to sometimes produce them. |
loicalleyne
pushed a commit
to loicalleyne/arrow
that referenced
this pull request
Nov 13, 2023
…e#38639) ### Rationale for this change The lint CI job is failing because an update to a dependency of lintr now does more strict DCF checking on the .lintr file ### What changes are included in this PR? The 'license' field was wrapped in quotes so that .lintr passes validation ### Are these changes tested? Yes, by existing CI job ### Are there any user-facing changes? No Authored-by: Dewey Dunnington <dewey@voltrondata.com> Signed-off-by: Antoine Pitrou <antoine@python.org>
assignUser
pushed a commit
to assignUser/arrow
that referenced
this pull request
Dec 1, 2023
…e#38639) ### Rationale for this change The lint CI job is failing because an update to a dependency of lintr now does more strict DCF checking on the .lintr file ### What changes are included in this PR? The 'license' field was wrapped in quotes so that .lintr passes validation ### Are these changes tested? Yes, by existing CI job ### Are there any user-facing changes? No Authored-by: Dewey Dunnington <dewey@voltrondata.com> Signed-off-by: Antoine Pitrou <antoine@python.org>
assignUser
pushed a commit
that referenced
this pull request
Jan 9, 2024
### Rationale for this change The lint CI job is failing because an update to a dependency of lintr now does more strict DCF checking on the .lintr file ### What changes are included in this PR? The 'license' field was wrapped in quotes so that .lintr passes validation ### Are these changes tested? Yes, by existing CI job ### Are there any user-facing changes? No Authored-by: Dewey Dunnington <dewey@voltrondata.com> Signed-off-by: Antoine Pitrou <antoine@python.org>
dgreiss
pushed a commit
to dgreiss/arrow
that referenced
this pull request
Feb 19, 2024
…e#38639) ### Rationale for this change The lint CI job is failing because an update to a dependency of lintr now does more strict DCF checking on the .lintr file ### What changes are included in this PR? The 'license' field was wrapped in quotes so that .lintr passes validation ### Are these changes tested? Yes, by existing CI job ### Are there any user-facing changes? No Authored-by: Dewey Dunnington <dewey@voltrondata.com> Signed-off-by: Antoine Pitrou <antoine@python.org>
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.
Rationale for this change
The lint CI job is failing because an update to a dependency of lintr now does more strict DCF checking on the .lintr file
What changes are included in this PR?
The 'license' field was wrapped in quotes so that .lintr passes validation
Are these changes tested?
Yes, by existing CI job
Are there any user-facing changes?
No