-
Notifications
You must be signed in to change notification settings - Fork 45
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
Is the assumption of a master branch prehaps incorrect? #107
Comments
Indeed - this was a quick hack to remap urls when 99.9% would have a Any suggestions for improvements to figure out the right url for these assets would be welcome. |
The background to me reading that code was/is trying to figure out why my readmes aren't being shown @ flows.nodered.org - e.g. this package What I believe I should be doing is having a And additionally add an error message to the blank package page @ flows.nodered.org saying: "add valid markdown readme to homepage link". EDIT: readme works fine at npmjs.com - hence there is a readme but its not showing @ flows.nodered.org - why I wonder! |
btw the api from gh can be used without token e.g. https://api.github.com/repos/gorenje/cdn.openmindmap.org/branches?per_page=10 - so that's one more request to get the branches for a repo. I guess from there one can look for either main or master or banana! EDIT: An example of how to do this is shown by this flow:
It takes a repo as input and gives back the contents of the readme. It finds a branch and readme file and returns the content of the first found. |
I was looking at this code - is the assumption of
master
to be the main branch or even a branch perhaps no longer applicable?The text was updated successfully, but these errors were encountered: