Re: travis-ci - fvwm.git master branch is "protected"

On Thu, Mar 24, 2016 at 05:48:55PM +0100, Viktor Griph wrote: > Is our strategy for handling of branches and pull requests summarized > anywhere? I'm working on that. Will put that out for tenure later on today. -- Thomas Adam

travis-ci - fvwm.git master branch is "protected"

Hi all, I've to document this formally, but I wanted to let you know of a few options I've enabled for the "master" branch on the main fvwm Git repository. All pushes by default (across all branches) will now have Travis CI ran against them. Travis is a Continuous Integration tool[1] which

Re: travis-ci - fvwm.git master branch is "protected"

Den 24 mar 2016 5:22 em skrev "Thomas Adam" : > > Hi all, > > I've to document this formally, but I wanted to let you know of a few options > I've enabled for the "master" branch on the main fvwm Git repository. > > All pushes by default (across all branches) will now have Travis

Re: FVWM website: WAS: [Re: FVWM code moved to Github]

On 24 March 2016 at 01:19, Dan Espen wrote: >> Thomas Adam writes: >> See previous paragraph, I do not think this is the right approach at all. > > I don't see the difference. > Right now Jason pulls from CVS to build the pages at fvwm.org. > He said he's

Re: travis-ci - fvwm.git master branch is "protected"

On Thu, Mar 24, 2016 at 05:48:55PM +0100, Viktor Griph wrote: > Cool. Would it be possible to stick some unit test framework to it as well? Sorry, Viktor, I missed this point the last time round. Yes, that's possible, and depending on how we decide to write unit tests, it can just hook into the

Thoughts about DEVELOPERS.md WAS: [travis-ci - fvwm.git master branch is "protected"]

"Thomas Adam" wrote: > I was thinking along the lines of this diff: > > https://github.com/fvwmorg/fvwm/commit/f81b2f4d7412813f12b235d8f1914409da0bbae9.patch > > Which you can view rendered here: > > https://github.com/fvwmorg/fvwm/blob/ta/git-docs/docs/DEVELOPERS.md > > What