hello,
there is a new endpoint for wasabi
Wasabi US East 2 (N. Virginia): s3.us-east-2.wasabisys.com
i am also contacting wasabi about this.
thanks,
hello,
there is a new endpoint for wasabi
Wasabi US East 2 (N. Virginia): s3.us-east-2.wasabisys.com
i am also contacting wasabi about this.
thanks,
You can make an issue on github:
thanks
........
Or even better make a pull request to fix
I think both me and @asdffdsa would like some hand-holding in the pull-requests. We want to contribute on the easier and more obvious stuff, but find the process confusing honestly. Could this be an idea for a sticky-post? Some of the general github guides I have looked at have been less-than-enlightening so I'm not sure if the setup here is slightly different - if the guide is out of date or what the deal is...
It just seems like this would be a good "investment" to get more pull-requests in the long run for you, thus lightening your load.
It isn't that easy making a pull request unfortunately!
I can write a step by step guide which will cover simple things, say editing a docs file.
It needs to use git which isn't the most user friendly command in the world.
It would go something like this (super abbreviated). There may be a GUI git which works well but I don't know how to use any of the GUI gits!
That would need expanding on what to do if your fix needs changing and expanding further on how to format go code and run tests.
Oh dear, are you telling me we need to install git just to edit a simple documentation text??..
Seems absurd that functionality wouldn't exist in the web...
I understand if adding code is more complex, but let's start with the simple stuff =P
It might be possible entirely on github for simple changes:
https://help.github.com/en/github/managing-files-in-a-repository/editing-files-in-your-repository
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.