Closed timholy closed 3 years ago
Puzzling, but the workflow is running here: https://github.com/timholy/Reexport.jl/runs/1612316499
When you add a new workflow, it is only executed on your personal fork, not on the target repository -- this is for security reasons.
Someone should also update the badge in the README.
Oh, and I guess this PR closes #25 :-)
simonster needs to set up a DOCUMENTER_KEY.
Seems unlikely to happen... :grimacing: This package doesn't use Documenter though, so is it really needed?
I'm no expert on these matters, but AFAIK TagBot needs some key for workflow-dispatch.
Hmm, okay. I'm okay with continuing to make git tags manually, and since Pkg doesn't care about git tags, I think it's okay for now. If you agree then I'll just go ahead and merge.
Sounds good. Perhaps we could also consider getting @simonster to agree to transfer the repository, or to add you with admin privileges?
That would definitely be ideal but no one has heard from him in quite some time, unfortunately.
travis.org is going away and travis.com will not be free. Moreover, the 1.0 release didn't get a tag. This switches to GitHub Actions for both activities.
simonster needs to set up a DOCUMENTER_KEY. Instructions can be found at https://github.com/julia-actions/MassInstallAction.jl/blob/a7872f2837e68e37857d0a8ea5b57acb101d8c8b/demos/MaintenanceDec2020/maintenance.jl#L29-L41