-
Notifications
You must be signed in to change notification settings - Fork 93
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
Switching to GitHub actions #95
Comments
I am fine with this. Good idea. My own docs only update when Travis is run, and will only publish the stable docs. If you want to remove this, and change the docs path, this is fine with me as well. |
@mvdnes Hello. How do you feel about transferring ownership of the repository? I think quite a significant amount has changed in the last few years, and it would be quite useful to get access to some of the more fine-grained project settings (in particular, branch protection and similar type stuff). |
Sure, I am fine with that. Have not looked at this repository in years, so it seems fitting. I just tried to transfer the ownership, but it complained that zesterer/spin-rs already exists. If you delete or rename that repository I can try again. |
There we go, it should be possible to transfer now. I hope I've been a good custodian of your project and I thank you for starting it! |
Now I am getting this error message: "zesterer already has a repository in the mvdnes/spin-rs network". I think you have been! What started out as some small code I needed for a specific use case, has grown a lot to help a lot of people! I think that is great. |
Ah. I renamed the repository, but did not delete it. I think I have everything I might want to keep locally in my repo anyway. I've now deleted it. |
Transfer is now pending! Good luck! |
@mvdnes I'm switching the repository CI over to GitHub actions. This will make CI automatically integrated with PRs and forks. I'm also switching the documentation in
Cargo.toml
over to the default docs.rs domain to avoid those using stable releases being redirected to unstable docs. I will, however, keep the documentation badge that redirects to your own URL to allow nightly docs to work fine.The text was updated successfully, but these errors were encountered: