-
Notifications
You must be signed in to change notification settings - Fork 942
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
allow to pass custom flags to rust:clippy #4001
Comments
This issue has been automatically marked as stale because it has not had recent activity. If you think this issue should stay open, please remove the If you're a maintainer, you can stop the bot to mark this issue as stale in the future by adding the |
bump |
This issue has been automatically marked as stale because it has not had recent activity. If you think this issue should stay open, please remove the If you're a maintainer, you can stop the bot to mark this issue as stale in the future by adding the |
bump |
This issue has been automatically marked as stale because it has not had recent activity. If you think this issue should stay open, please remove the If you're a maintainer, you can stop the bot to mark this issue as stale in the future by adding the |
Bump |
Added the backlog label so you no longer need to bump to keep it alive. This change request is one of a number that relate to individual customization of linters that we should plan to address. Feel free to open a pull request if you would like to work on this or we can let you know when we plan to start addressing linter configuration as a whole. |
Wonderful, thanks so much Zack! |
|
Skip to main content Headings A first-level headingA second-level headingA third-level headingScreenshot of rendered GitHub Markdown showing sample h1, h2, and h3 headers, which descend in type size and visual weight to indicate descending hierarchy level. When you use two or more headings, GitHub automatically generates a table of contents that you can access by clicking within the file header. Each heading title is listed in the table of contents and you can click a title to navigate to the selected section. Screenshot of the README file in the GitHub Docs open source repository with the drop-down menu for the table of contents exposed. The table of contents icon is outlined in dark orange. Styling text Style Syntax Keyboard shortcut Example Output Text that is not a quote
Screenshot of rendered GitHub Markdown showing sample quoted text. The quote is indented with a vertical line on the left, and its text is dark gray rather than black. Note: When viewing a conversation, you can automatically quote text in a comment by highlighting the text, then typing R. You can quote an entire comment by clicking , then Quote reply. For more information about keyboard shortcuts, see "Keyboard shortcuts." Quoting code Use To format code or text into its own distinct block, use triple backticks. Some basic Git commands are:
Screenshot of rendered GitHub Markdown showing a code block. The words "git status," "git add," and "git commit" appear in a fixed-width typeface, highlighted in light gray. For more information, see "Creating and highlighting code blocks." If you are frequently editing code snippets and tables, you may benefit from enabling a fixed-width font in all comment fields on GitHub. For more information, see "About writing and formatting on GitHub." Supported color models The background color is Here are the currently supported color models. Color Syntax Example Output A supported color model cannot have any leading or trailing spaces within the backticks. You can also create a Markdown hyperlink by highlighting the text and using the keyboard shortcut Command+V. If you'd like to replace the text with the link, use the keyboard shortcut Command+Shift+V. This site was built using GitHub Pages. Screenshot of rendered GitHub Markdown showing how text within brackets, "GitHub Pages," appears as a blue hyperlink. Note: GitHub automatically creates links when valid URLs are written in a comment. For more information, see "Autolinked references and URLs." Section links Screenshot of a README for a repository. To the left of a section heading, a link icon is outlined in dark orange. Relative links A relative link is a link that is relative to the current file. For example, if you have a README file in root of your repository, and you have another file in docs/CONTRIBUTING.md, the relative link to CONTRIBUTING.md in your README might look like this: Contribution guidelines for this project Relative links are easier for users who clone your repository. Absolute links may not work in clones of your repository - we recommend using relative links to refer to other files within your repository. Images Screenshot of a comment on a GitHub issue showing an image, added in the Markdown, of an Octocat smiling and raising a tentacle. GitHub supports embedding images into your issues, pull requests, discussions, comments and .md files. You can display an image from your repository, add a link to an online image, or upload an image. For more information, see "Uploading assets." Note: When you want to display an image that is in your repository, use relative links instead of absolute links. Here are some examples for using relative links to display an image. Context Relative Link For more information, see "Relative Links." Specifying the theme an image is shown to For example, the following code displays a sun image for light themes and a moon for dark themes: Lists
To order your list, precede each line with a number.
Nested Lists To create a nested list using the web editor on GitHub or a text editor that uses a monospaced font, like Visual Studio Code, you can align your list visually. Type space characters in front of your nested list item until the list marker character (- or *) lies directly below the first character of the text in the item above it.
Screenshot of Markdown in Visual Studio Code showing how indented bullets align vertically with the first letter of the text lines above them. Screenshot of rendered GitHub Markdown showing a numbered item followed by a bulleted item nested one level to the right, and another bulleted item nested yet further to the right. To create a nested list in the comment editor on GitHub, which doesn't use a monospaced font, you can look at the list item immediately above the nested list and count the number of characters that appear before the content of the item. Then type that number of space characters in front of the nested list item. In this example, you could add a nested list item under the list item 100. First list item by indenting the nested list item a minimum of five spaces, since there are five characters (100 .) before First list item.
You can create multiple levels of nested lists using the same method. For example, because the first nested list item has seven characters (␣␣␣␣␣-␣) before the nested list content First nested list item, you would need to indent the second nested list item by at least two more characters (nine spaces minimum).
For more examples, see the GitHub Flavored Markdown Spec. Task lists
If a task list item description begins with a parenthesis, you'll need to escape it with :
For more information, see "About task lists." Mentioning people and teams Note: A person will only be notified about a mention if the person has read access to the repository and, if the repository is owned by an organization, the person is a member of the organization. @github/support What do you think about these updates? Screenshot of rendered GitHub Markdown showing how the team mention "@github/support" renders as bold, clickable text. When you mention a parent team, members of its child teams also receive notifications, simplifying communication with multiple groups of people. For more information, see "About teams." Typing an @ symbol will bring up a list of people or teams on a project. The list filters as you type, so once you find the name of the person or team you are looking for, you can use the arrow keys to select it and press either tab or enter to complete the name. For teams, enter the @organization/team-name and all members of that team will get subscribed to the conversation. The autocomplete results are restricted to repository collaborators and any other participants on the thread. Referencing issues and pull requests For more information, see "Autolinked references and URLs." Referencing external resources Uploading assets Using emoji @octocat 👍 This PR looks great - it's ready to merge! Screenshot of rendered GitHub Markdown showing how emoji codes for +1 and shipit render visually as emoji. Typing : will bring up a list of suggested emoji. The list will filter as you type, so once you find the emoji you're looking for, press Tab or Enter to complete the highlighted result. For a full list of available emoji and codes, see the Emoji-Cheat-Sheet. Paragraphs Footnotes Here is a simple footnote1. A footnote can also have multiple lines2. Screenshot of rendered Markdown showing superscript numbers used to indicate footnotes, along with optional line breaks inside a note. Note: The position of a footnote in your Markdown does not influence where the footnote will be rendered. You can write a footnote right after your reference to the footnote, and the footnote will still render at the bottom of the Markdown. Footnotes are not supported in wikis. Alerts Issues Multiple types of alerts are available. You can add an alert with a special blockquote line that specifies the alert type, and then add the alert information in a standard blockquote immediately after. Note Highlights information that users should take into account, even when skimming. Tip Optional information to help a user be more successful. Important Crucial information necessary for users to succeed. Warning Critical content demanding immediate user attention due to potential risks. Caution Negative potential consequences of an action. Screenshot of rendered Markdown alerts showing how Note, Tips, Important, Warning, and Caution render with different colored text and icons. Hiding content with comments Ignoring Markdown formatting Let's rename *our-new-project* to *our-old-project*. Screenshot of rendered GitHub Markdown showing how backslashes prevent the conversion of asterisks to italics. The text reads, "Let's rename our-new-project to our-old-project." For more information on backslashes, see Daring Fireball's "Markdown Syntax." Note: The Markdown formatting will not be ignored in the title of an issue or a pull request. Disabling Markdown rendering Screenshot of a Markdown file in a GitHub repository showing options for interacting with the file. A button, labeled "Code", is outlined in dark orange. Disabling Markdown rendering enables you to use source view features, such as line linking, which is not possible when viewing rendered Markdown files. Further reading Privacy policy Learn how to contribute Still need help? Footnotes |
Is your feature request related to a problem? Please describe.
In our current rust linting GHA workflow we're running clippy by issuing the following command:
cargo clippy --verbose --tests --benches -- -D clippy::all
.Describe the solution you'd like
Add ENVVAR to super-linter:
CLIPPY_FLAGS
, so I could set it like this:Describe alternatives you've considered
not sure
Additional context
N/A
The text was updated successfully, but these errors were encountered: