Skip to content

fix: update ranger file #3065

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Apr 7, 2021
Merged

fix: update ranger file #3065

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions .github/ranger.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,12 +4,10 @@ default:
close:
# Default time to wait before closing the label. Can either be a number in milliseconds
# or a string specified by the `ms` package (https://www.npmjs.com/package/ms)
delay: "3 days"
delay: "2 days"

# Default comment to post when an issue is first marked with a closing label
comment: "⚠️ This issue has been marked $LABEL and will be closed in $DELAY."
close-faster:
delay: "1 minute"

labels:
duplicate: close
Expand All @@ -26,7 +24,7 @@ labels:
delay: 5s
message: "Thanks for making your first contribution! :slightly_smiling_face:"
extension-request:
action: close-faster
action: close
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jsjoeio Ah that's too bad that there's no schema validator for these, I would expect some sort of warning if fields are unknown

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right? Well based on what I read and saw in the config, I just assumed I could create my own custom actions like this: https://github.com/cdr/code-server/pull/3065/files#diff-15592ca299f8c76c553cc34e528b303896afa722a32d8f983cdcf67dfa7b38f1L11-L12

But turns out that is not the case 😂

delay: 5s
message: >
Thanks for opening an extension request!
Expand All @@ -38,7 +36,7 @@ labels:
file and then installing into code-server as a temporary workaround.
See [docs](https://github.com/cdr/code-server/blob/main/docs/FAQ.md#installing-vsix-extensions-via-the-command-line) for more info."
"upstream:vscode":
action: close-faster
action: close
delay: 5s
comment: >
This issue has been marked as 'upstream:vscode'.
Expand Down