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

Update and improve another few URLs #1628

Merged
merged 2 commits into from
Oct 15, 2024

Conversation

EliahKagan
Copy link
Member

This builds on 65f69f7 (#1624, see also #1624 (comment)), completing the third task in #1627 (gix-diff/src/tree/function.rs:27), fixing a broken link and updating another. See 991c939 for details.

This does not do the first or second task of #1627 because I have not (yet?) figured out how. I think those improvements could go in another PR, once the best solution is figured out.

I've also improved on 1ea08bf (#1624) by giving the nonexistent repo used for a 401 response the more self-documenting name nonexistent. See baa6f23 for the rationale and a few details.

This updates the "git_cmp_c" and "git_cmp_rs" links in the
`gix_diff::tree::function::diff` documentation comment.

- The significant change is to the "git_cmp_rs" link (the second
  link), which accounts for how files have renamed and how code has
  been moved, and also changed in GitoxideLabs#849 to fix issue GitoxideLabs#848.

  This hyperlink change completes the third task listed in GitoxideLabs#1627.

- The other change is to update the "git_cmp_c" link at the same
  time. That code has not changed, and this is just referring to a
  later commit (the current tip of the master branch in git/git).

  The reason to also do this change is to make it easier to verify,
  both now and for anyone reading the documentation, that that link
  remains current.
The nonexistent repo used to get data from a 401 response in the
`update-curl-fixtures` rule was formerly called `foo`. (In 1ea08bf
in GitoxideLabs#1624, I had erroneously said this was for a 404 response, but
the `foo` URL is the 401 URL, not the 404 URL.) This commit renames
it to `nonexistent`, which is more self-documenting and less likely
to be created by accident, even temporarily.

In 1ea08bf (GitoxideLabs#1624), it was changed from `Byron/foo` to
`GitoxideLabs/foo`, going along with the change of the existing
repository (gitoxide's own) from `Byron/gitoxide` to
`GitoxideLabs/gitoxide`. But while `Byron/foo` would continue not
to exist as long as the convention of not having a `foo` repo was
maintained by `@Byron`, a `foo` repository in `GitoxideLabs` might
someday be created by another developer who is not aware of its
status in `Makefile`. Renaming it to `nonexistent` should make this
easier to avoid.

I tested this change with the same approach as noted for 1ea08bf.
Copy link
Member

@Byron Byron left a comment

Choose a reason for hiding this comment

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

Thanks a lot for finding the new spot of these references :)!

@Byron Byron merged commit 4cff32c into GitoxideLabs:main Oct 15, 2024
16 checks passed
@EliahKagan EliahKagan deleted the update-git-cmp-rs-url branch October 15, 2024 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants