Gogs port: A painless self-hosted Git service
Chris H
bsd-lists at bsdforge.com
Wed Dec 16 19:10:04 UTC 2015
On Wed, 16 Dec 2015 01:52:38 -0800 Yuri <yuri at rawbw.com> wrote
> On 12/13/2015 23:54, Torsten Zühlsdorff wrote:
> > I did this often for different processes. I won't work on the issue
> > this year - there is do much open to do.
> >
> > But please write me a desired workflow and the needed requirements and
> > i will do this in the next year. Just 3 weeks to go :D
>
> This isn't a complete workflow, but here is an idea for port updates:
> Each port update or new port submission could become a pull request.
> Once the new pull request is created, system should launch poudriere
> builds for it for all required platforms, and append the notice that
> builds have started. Then append the build status. If it was successful,
> committer can just approve the change with one press of a button. I
> believe there is a way to do a two way sync between git and subversion.
> If at any point in time that port changes, the process has to be
> invalidated and restarted if the pull request is still mergeable, or
> submitter should be notified if it became unmergeable.
>
> This could simplify and expedite the process of committing of port changes.
Much of the workflow you describe above, appears to have already
been done:
http://www.theoldmonk.net/gitzilla/ (documentation)
https://github.com/gera/gitzilla (gitzilla, itself)
HTH
--Chris
>
> Yuri
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
More information about the freebsd-ports
mailing list