Yes, concerning CircleCI, I have checked it, and it is orthogonal here. The GitHub pipeline is triggered only for tag pushes, while CircleCI concerns the PRs and integration purposes.
Given that for the release, I just wanted to provide a tooling concerning the Github functionalities themselves, and so quite naturally, the Github pipeline is working out-of-the-box here. It is entirely possible to do it with CircleCI, but it requires to install the GH CLI and generate a token that is the stored on CircleCI side. On top of being more work, I tend, from a security standpoint, to avoid having a token of a system hanging out in another system if I can... Regards, Adrien Ferrand Le jeu. 13 août 2026, 17:46, G.W. Haywood <[email protected]> a écrit : > Hi there, > > On Thu, 13 Aug 2026, Adrien Ferrand wrote: > > > ...also think we have to deal with [Github] at least on the shorter > terms. > > Agreed. > > > I have proposed a pipeline for the Github-specific activities during > release ... > > Did you check out what's already there? Look in the .circleci directory. > > > Concerning the delivery of the release tarball ... documentation > > states (so far) that the release tarball is distributed through the > > release pages in the Github project, so we should either have it > > that way to not have end-users puzzled ... > > Agreed. > > -- > > 73, > Ged. > > > _______________________________________________ > BackupPC-users mailing list > [email protected] > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: https://github.com/backuppc/backuppc/wiki > Project: https://backuppc.github.io/backuppc/ >
_______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
