[GH-ISSUE #158] broken link #6091

Closed
opened 2026-06-17 04:32:57 -05:00 by GiteaMirror · 6 comments
Owner

Originally created by @fccm on GitHub (Aug 28, 2013).
Original GitHub issue: https://github.com/semver/semver/issues/158

On the French translation page, the link to the Russian translation is wrong.

Originally created by @fccm on GitHub (Aug 28, 2013). Original GitHub issue: https://github.com/semver/semver/issues/158 On the French translation page, the link to the Russian translation is wrong.
Author
Owner

@bessarabov commented on GitHub (Aug 28, 2013):

Created pull request that fixes this: https://github.com/mojombo/semver.org/pull/77

<!-- gh-comment-id:23420847 --> @bessarabov commented on GitHub (Aug 28, 2013): Created pull request that fixes this: https://github.com/mojombo/semver.org/pull/77
Author
Owner

@bessarabov commented on GitHub (Aug 28, 2013):

This issue is fixed so it can be closed (sorry, I can't do it myself =)

<!-- gh-comment-id:23424667 --> @bessarabov commented on GitHub (Aug 28, 2013): This issue is fixed so it can be closed (sorry, I can't do it myself =)
Author
Owner

@haacked commented on GitHub (Aug 28, 2013):

Ah, next time you fix an issue, just add "fixes #158" (where 158 is the issue number) to your commit message or your pull request message. Then when the PR is merged, it'll automatically close the issue! Cool, right?

<!-- gh-comment-id:23424882 --> @haacked commented on GitHub (Aug 28, 2013): Ah, next time you fix an issue, just add "fixes #158" (where 158 is the issue number) to your commit message or your pull request message. Then when the PR is merged, it'll automatically close the issue! Cool, right?
Author
Owner

@bessarabov commented on GitHub (Aug 28, 2013):

=) Yes, I have forgotten about this feature, thx for reminding =) But I'm not sure that that would work — the commit was to the repo semver.org, but the issue that had to be closed was in the other repo semver.

<!-- gh-comment-id:23425134 --> @bessarabov commented on GitHub (Aug 28, 2013): =) Yes, I have forgotten about this feature, thx for reminding =) But I'm not sure that that would work — the commit was to the repo `semver.org`, but the issue that had to be closed was in the other repo `semver`.
Author
Owner

@haacked commented on GitHub (Aug 28, 2013):

That also works! It's a recent new feature. You would write: "Fixes mojombo/server#158"

<!-- gh-comment-id:23425290 --> @haacked commented on GitHub (Aug 28, 2013): That [also works](https://github.com/blog/1439-closing-issues-across-repositories)! It's a recent new feature. You would write: "Fixes mojombo/server#158"
Author
Owner

@bessarabov commented on GitHub (Aug 28, 2013):

Thank you! I havn't knew it. Great to have this feature =)

<!-- gh-comment-id:23425624 --> @bessarabov commented on GitHub (Aug 28, 2013): Thank you! I havn't knew it. Great to have this feature =)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/semver#6091