Skip to content
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

docs: update irrelvant links #33784

Merged
merged 2 commits into from
Jul 8, 2024

Conversation

gagan-bhullar-tech
Copy link
Contributor

Why: Update irrelevant links to npm registry

Closes: #33776

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

  • I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

    • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.
  • For content changes, I have completed the self-review checklist.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jul 1, 2024
@nguyenalex836 nguyenalex836 added content This issue or pull request belongs to the Docs Content team actions This issue or pull request should be reviewed by the docs actions team and removed triage Do not begin working on this issue until triaged by the team labels Jul 1, 2024
@nguyenalex836
Copy link
Contributor

@gagan-bhullar-tech Hello! 👋 Thank you for opening a PR!

We will need to put this PR on hold for now until the issue this PR is linked to has been reviewed by the team 💛

Copy link
Contributor

github-actions bot commented Jul 2, 2024

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
actions/publishing-packages/publishing-java-packages-with-gradle.md fpt
ghec
ghes@ 3.13 3.12 3.11 3.10 3.9
fpt
ghec
ghes@ 3.13 3.12 3.11 3.10 3.9
actions/publishing-packages/publishing-java-packages-with-maven.md fpt
ghec
ghes@ 3.13 3.12 3.11 3.10 3.9
fpt
ghec
ghes@ 3.13 3.12 3.11 3.10 3.9

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

Copy link
Contributor

@hubwriter hubwriter left a comment

Choose a reason for hiding this comment

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

@gagan-bhullar-tech - Thanks for making this correction.
👍

We'll get this merged next week when the current repo freeze is lifted.

@hubwriter hubwriter enabled auto-merge July 2, 2024 11:01
@nguyenalex836 nguyenalex836 added the ready to merge This pull request is ready to merge label Jul 2, 2024
@hubwriter hubwriter added this pull request to the merge queue Jul 7, 2024
Merged via the queue into github:main with commit b8cdb50 Jul 8, 2024
52 of 53 checks passed
Copy link
Contributor

github-actions bot commented Jul 8, 2024

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
actions This issue or pull request should be reviewed by the docs actions team content This issue or pull request belongs to the Docs Content team ready to merge This pull request is ready to merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Irrelevant link to npm registry in pages about publishing Java packages in GitHub
3 participants