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

Fixes wrong link in CONTRIBUTING.md #81809

Closed
wants to merge 1 commit into from
Closed

Fixes wrong link in CONTRIBUTING.md #81809

wants to merge 1 commit into from

Conversation

raziel
Copy link
Contributor

@raziel raziel commented Jul 20, 2022

The link to the "Where or how should I add documentation" had some extra characters.

Fixes #ISSUE_NUMBER

The link to the "Where or how should I add documentation" had some extra characters.
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Jul 20, 2022

🔗 Helpful links

✅ No Failures (0 Pending)

As of commit 1043d75 (more details on the Dr. CI page):

Expand to see more

💚 💚 Looks good so far! There are no failures yet. 💚 💚


This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

@raziel raziel requested a review from zou3519 July 20, 2022 20:31
@kit1980
Copy link
Member

kit1980 commented Jul 23, 2022

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a merge job. Check the current status here

@github-actions
Copy link

Hey @raziel.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

facebook-github-bot pushed a commit that referenced this pull request Jul 26, 2022
Summary:
The link to the "Where or how should I add documentation" had some extra characters.

Fixes #ISSUE_NUMBER

Pull Request resolved: #81809
Approved by: https://github.com/zou3519

Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/0985188c8fa2ffe8cba7c8a1bd32ec6d045940d3

Reviewed By: osalpekar

Differential Revision: D38120067

Pulled By: raziel

fbshipit-source-id: 838c4ce795d4b5f3562730659edb909d093724e5
@github-actions github-actions bot deleted the raziel-patch-1 branch February 18, 2024 01:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants