Cannot establish repo name from Git remote
See original GitHub issueFirst off, I want to thank you for this very interesting project!
I was trying to use portray
for my project, and found that it broke when I tried to run
portray in_browser
It said
UserWarning: Unable to identify `repo_name` and `repo_url` automatically
I looked through the code and found that this was issued because portray
could not determine the name of my project from the git remote. I seldom use http
for cloning, preferring ssh
myself and since I also use Azure Devops during working hours I have remotes looking like
username@vs-ssh.visualstudio.com:v3/username/projectname/reponame
This origin
-remote will be ignored by the if-clause in config.py#L141.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Managing remote repositories - GitHub Docs
This error means that the remote name you want to use already exists. To solve this, either use a different remote name, or...
Read more >github - Git - remote: Repository not found - Stack Overflow
My solution was to create the repo directly on github.com via the web page. Everything worked smoothly after that. I had been assuming...
Read more >2.5 Git Basics - Working with Remotes
If you clone a repository, the command automatically adds that remote repository under the name “origin”. So, git fetch origin fetches any new...
Read more >Push commits to an additional Git repository - AWS CodeCommit
To push the commit from the local repo to your remote repositories, run git push -u remote-name branch-name where remote-name is the nickname...
Read more >How to Add a New Remote to your Git Repo
To add a new remote, use the git remote add command on the terminal, in the directory your repository is stored at. The...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve included repo discovery improvements and additional documentation in the just released 1.3.0 version of portray.
I’ve added a guide on how to deal with the warning and what it means in the updated troubleshooting guide
@hbldh It turns out I’m able to often determine the http link from a the ssh URL making it useful. User configs will indeed take precedence over any auto determinations.
@sindrehan Happy to help! Agreed! I’ve made this change in the lastest release, empowering users to remove this warning.
Thanks!
~Timothy
@timothycrosley Ah, I see, thanks! I just did a quick grep over the repo for
repo_url
andrepo_name
and could only find references to where the values are set, but since they’re passed to mkdocs that makes sense.Also, I think it would make sense to not raise a warning if the user has specified the url/name manually.