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

code-review does not respect code-review-gitlab-base-url #208

Open
innerout opened this issue Apr 3, 2022 · 2 comments
Open

code-review does not respect code-review-gitlab-base-url #208

innerout opened this issue Apr 3, 2022 · 2 comments

Comments

@innerout
Copy link

innerout commented Apr 3, 2022

Describe the bug
code-review does not respect when the below variables are set. This seems to apply to github and gitlab custom instances as discovered by @gagbo in the doom emacs discord.

(setq code-review-gitlab-base-url "custom.url")
(setq code-review-gitlab-host "remaining.com/api")
(setq code-review-gitlab-graphql-host "remaining.com/api")

To Reproduce
Steps to reproduce the behavior:
Add this in your init.el

(setq code-review-gitlab-base-url "custom.url")
(setq code-review-gitlab-host "remaining.com/api")
(setq code-review-gitlab-graphql-host "remaining.com/api")
  1. Go to magit-status
  2. Open a MR that is yet to be merged.
  3. Execute code-review-forge-pr-at-point
  4. See the error code-review prepends gitlab. even when code-review-gitlab-base-url is set.

Expected behavior
Respect and concatenate code-review-gitlab-base-url with host and graphql-host properly.

Screenshots
image

Desktop (please complete the following information):

  • OS: ArchLinux
  • emacs version: emacs-pgtk-native-comp
  • Latest doom emacs version
@hjudt
Copy link
Contributor

hjudt commented Apr 4, 2022

This might just be a cosmetic issue, see issue #48. Just be stubborn and proceed; I had to enter a user and confirm "set globally" three times. See the linked issue.

@innerout
Copy link
Author

innerout commented Apr 4, 2022

Thanks! I missed the issue you mentioned. The behavior you describe seems like mine, still having unexpected behavior makes the package counterintuitive to use. I believe if the package uses the variables mentioned in my first post, things will work as expected as in magit-forge.

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

No branches or pull requests

2 participants