Skip to content

Use master for input and some other branch for the output #2

@shelajev

Description

@shelajev

Currently the master branch is used for the site output. Changes are pushed to the asciidoc branch, and Travis pushes the generated site to master from which the site is served.

In the process it overwrites changes to the master, which could be useful. Like having the license file and the readme.

As a developer I'd like to come to the repository and see a README.md and the LICENSE.md so I know what I can do with the code.

Can we please use the master branch for the input (and people) and asciidoc or some other branch for the output?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions