-
Notifications
You must be signed in to change notification settings - Fork 39
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
Make github releases from CI #6
base: main
Are you sure you want to change the base?
Conversation
deploy: | ||
provider: releases | ||
api_key: | ||
secure: bQWQ1CfKebdRitqps2mto7LLjlbut6tYmmv92/r2jbZa4RILulnyuBQiroKv96hxCZLH5WHRenVBROL7Sd2BZgAMGJgm0sPt5DRB/NxGHTOiW4LkgzzIQr7ViWBiz+pVAjIUaPRBFz/d5KJv0bIsrvSqZ2OTH0DonK+JmCs4luPqnhGJQG+VC25WRV/E2Jn3CGo7Nm/hTFP/CZxi9IPGpf6SQ9FMsJQ38viFUQyuhE3DcbeQe9ZkL4tltxqbP+cKoR569MovJNqdfPlBYijnwRnNuBSojAK2xsrfHQDwwHYQFg0ViAf+ubWcaY8OjRDZTnHqiT8E7RFUMImEZy7zPu+KCoXUNPfWl7PfnpWjiKcz2SOidJKfeH390hsorumv8NkgQnsw3PSCZhEhRhPZ1GWQWa5aCVI7YaNFip/5JzTifaibw6cFxla9pW/EcwTKJQ2drx+5oduvoedlpPd1k7JAgbUo0nItNC9dkIZ+pOUTyZp36+Ztxwj58cnz2pLlIjntzp0HwiH26iCeUkQdlqMAJca0IOGx0y6u1xhpftHppgGHz+1fQjTkGv81yBiNZiUudulrMbIaAFdfPtEmrXfKqNPAVa0EoiTA533CZSuiIP7mAFZIpv/saKtV5a6F4KpJ46FheJYCm8PCAX5pwil6EXUb/UiLS5UOYnRBpaE= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like you might have published some information that you should not have published!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, perhaps. But this was before we moved the repo to the magit organization, so it only refers to my own CI for libegit2, which I've since deleted.
I've been trying to forget about this PR. 😞
Would you also be interested in Releases build from the OpenSUSE Buildservice? |
Probably not. I am completely unfamiliar with OpenSUSE Buildservice; I don't even know if that is a general purpose CI or just builds packages for OpenSUSE. And I don't think I would get much out of learning more about this platform. I have just removed the Travis setup. Appversor is still there because there new pushes still result in builds (but they seem to fail). I would like to use a single CI platform, Github Actions. That supports linux, macos and windows, I believe. |
Besides Windows you can build packages for any platform there, it's a ci for software packages. |
So it is a competitor to Github Actions / Travis / Appversor etc. I don't want to learn about yet another of those at this time. In the past I have merged pull-requests that implemented "better CI" in one way or another, without having the knowledge to really understand and maintain the new tool chain. And then something broke, the original contributor wasn't interested anymore in helping me deal with that, and I was forced to choose between learning about the new toolchain or discard the changes to go back to a simpler setup that I actually understand. So to go back to your question:
No, I don't. I don't see any benefit in that, but that might be due to my ignorance. This is one of many things I do not know anything about and I have feeling that learning about other such things would be more beneficial than learning about this thing. If this package were already actually being used by Magit, then the story might be different. But right now, this is just something that I have to maintain without actually benefiting from it at all. (That will hopefully change at some point, but that could still be a long way off.) So thanks for the offer to implement "Releases build from the OpenSUSE Buildservice", but at this time this contribution would just be more work for me. |
Jonas Bernoulli ***@***.***> writes:
So it is a competitor to Github Actions / Travis / Appversor etc.
Kinda but more on the Linux package manager level.
So to go back to your question:
> Would you also be interested in Releases build from the OpenSUSE Buildservice?
No, I don't. I don't see any benefit in that, but that might be due to
my ignorance. This is one of many things I do not know anything about
and I have feeling that learning about other such things would be more
beneficial than learning about this thing.
If this package were already actually being used by Magit, then the
story might be different. But right now, this is just something that I
have to maintain without actually benefiting from it at all. (That
will hopefully change at some point, but that could still be a long
way off.)
So thanks for the offer to implement "Releases build from the OpenSUSE
Buildservice", but at this time this contribution would just be more
work for me.
No problem. I created a package on the obs for my own use, if you want
to add a link to it you can find it here:
https://build.opensuse.org/package/show/home:Thaodan:emacs/emacs-libgit
```
[![build
result](https://build.opensuse.org/projects/home:Thaodan:emacs/packages/emacs-libgit/badge.svg?type=default)](https://build.opensuse.org/package/show/home:Thaodan:emacs/emacs-libgit)
```
|
No description provided.