Skip to content

https://github.com/github/docs/issues/new/choose #46255

Description

@ali0935ni2

Code of Conduct

What article on docs.github.com is affected?

  • [](url)

What part(s) of the article would you like to see updated?

.devcontainer/Dockerfilehttps://github.com/github/docs/issues/new/choose# Update ARG and FROM together from the Node devcontainer image tags:

https://mcr.microsoft.com/en-us/product/devcontainers/javascript-node/tags

ARG VARIANT=dev-24-bookworm
FROM mcr.microsoft.com/devcontainers/javascript-node:dev-24-bookworm@sha256:c39e4aaf0c7c4da594f845aeb98d37510343bff178b320a6f7e9e2e95ca7957e# Customizing how changed files appear on GitHub

To keep certain files from displaying in diffs by default, or counting toward the repository language, you can mark them with the linguist-generated attribute in a .gitattributes file.

Use a .gitattributes file to mark files that match a given "pattern" with the specified attributes. A .gitattributes file uses the same rules for matching as .gitignore files. For more information, see PATTERN FORMAT in the Git documentation.

  1. Unless the .gitattributes file already exists, create a .gitattributes file in the root of the repository.

  2. Use the linguist-generated attribute to mark or unmark paths that you would like to be ignored for the repository's language statistics and hidden by default in diffs.

    For example, to mark search/index.json as a generated file, add this line to .gitattributes:

    search/index.json linguist-generated
    

    To unmark a file that would generally be considered generated, add this line to .gitattributes:

    bootstrap.min.css -linguist-generated
    

Further reading

Additional information

No response

Activity

  1. added
    contentThis issue or pull request belongs to the Docs Content team
    on Oct 10, 2026
  2. added
    invalidThis issue/PR is invalid
    and removed
    contentThis issue or pull request belongs to the Docs Content team
    on Oct 10, 2026
  3. docs-bot commented on Oct 10, 2026

    @docs-bot
    Collaborator

    This issue may have been opened accidentally. I'm going to close it now, but feel free to open a new issue with a more descriptive title! Make sure not to include full URLs in your issue titles, and use paths instead.

  4. added
    triageDo not begin working on this issue until triaged by the team
    on Oct 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    invalidThis issue/PR is invalidtriageDo not begin working on this issue until triaged by the team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions