-
Notifications
You must be signed in to change notification settings - Fork 43
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
Time to switch to GitHub Actions? #92
Comments
no idea, all the links error out. Probably we should move CI to Github actions but I don't know how to do that. (GitHub actions have the annoying feature that they aren't version controlled.. shocking!) |
I don't know why we even switch to travis.com since travis.org is still working.. |
In my repository, migrating travis.org to travis.org was easy (just clicking some buttons), so I don't know why the tests are not running... |
Taking this opportunity, I'm trying to switch Travis to GitHub Actions in my repository for an experiment. I succeeded to enable GitHub Actions, but, I couldn't figure out how to disable the checks for travis. Do you have any ideas? |
Here's an instruction. 1. Configure repository on GitHubGenerate keys by DocumenterTools.jl julia> using DocumenterTools
julia> Travis.genkeys(user="JuliaApproximation", repo="[email protected]:JuliaApproximation/FastGaussQuadrature.git")
<keys will be generated here.> Add Deploy keysadd Deploy key which begin Add Secret keyadd Secret key which which is longer than deploy key. 2. Update code in the repositoryAdd
|
@dlfivefifty |
versioning of the GitHub action: at the moment the actions are copied and pasted from somewhere else and when they change one has to fix it. Seems like a very bad design |
Do you mean |
Touchè |
Okay, I'll make a PR. |
These secret key and deploy key are required to deploy a document by Documenter.jl. |
OK I followed the instructions and pushed the changes, does that work? |
Ah, sorry for confusing..., I've already sent a PR(#93).
|
The tests have failed because the doctest is incomplete. This problem is solved by this commit in PR(#93). |
It's better if we can merge the PR(#93), but there are some conflicts. 1. Reset the commit and merge the PR(#93)On your terminal
and then merge #93. 2. Make a new PR to solve the doctest problemIn this case, I'll make a new PR instead of #93. 3. Add @hyrodium as collaborator for this repository, and add permissionHe wil solve this problem with option1 (reset & merge PR). |
OK I merged the PR and added you as a maintainer |
Thanks! |
What is up with this message?
The text was updated successfully, but these errors were encountered: