Skip to content

Potential duplication of content for the the Dependabot private registry documentation #41895

Closed

Description

@yeikel

Code of Conduct

What article on docs.github.com is affected?

The following entries appear to cover the same topic and may be duplicates. After reviewing them, it’s unclear what distinguishes the two or why both are needed

https://docs.github.com/en/code-security/dependabot/working-with-dependabot/configuring-access-to-private-registries-for-dependabot
https://docs.github.com/en/code-security/dependabot/working-with-dependabot/guidance-for-the-configuration-of-private-registries-for-dependabot

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

I think that we should consolidate the information under a single article and keep one or the other

Additional information

I noticed this issue while working on #41793

Activity

  1. added
    contentThis issue or pull request belongs to the Docs Content team
    on Dec 16, 2025
  2. added
    triageDo not begin working on this issue until triaged by the team
    on Dec 16, 2025
  3. changed the title [-]Potential duplication in content in the Dependabot private registry documentation[/-] [+]Potential duplication of content for the the Dependabot private registry documentation[/+] on Dec 16, 2025
  4. Sharra-writes commented on Dec 30, 2025

    @Sharra-writes
    Contributor

    @yeikel Thanks for pointing this out! I believe code security is coming up on our list of docs sets that need to be reorganized, so I will make this an internal issue and tag it for that project. That should help keep it on our radar as we're moving information around.

  5. added
    code securityContent related to code security
    fix-internallyTriggers a workflow to copy the issue internally and close the current issue
    and removed
    triageDo not begin working on this issue until triaged by the team
    on Dec 30, 2025
  6. docs-bot commented on Dec 30, 2025

    @docs-bot
    Collaborator

    Thank you for opening this issue! Updates to this documentation must be made internally. I have copied your issue to an internal issue, so I will close this issue.

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

    code securityContent related to code securitycontentThis issue or pull request belongs to the Docs Content teamfix-internallyTriggers a workflow to copy the issue internally and close the current issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions