Steps contributing the documentation

Liquibase Development
1

Thank you so much for your willingness to contribute! I very much appreciate the effort.

Steps 3-6 are not currently being handled by CI, it is something that we are doing manually on an as-needed basis. 

Next steps for you would be to submit the PR to liquibase (against the 3.8.x branch) and mark it as a documentation fix. I will then make sure it gets moved though the system.

When I generate the documentation I will create a PR against the staging branch, where the results can then be previewed (there is a CI solution set up right now that publishes to http://staging.liquibase.org/) and then I typically merge from staging to master after a day or so, sometimes sooner. There is an automatic process at github to publish any changes pushed to master. 

For changes in non-generated documentation, please make a PR that targets the staging branch of the liquibase.github.com repository. I have been reviewing and approving and merging those as they come in. 

Steve Donie
Principal Software Engineer
Liquibase Community Engagement
Datical, Inc. http://www.datical.com/

2

I see that you have submitted PR #964 - https://github.com/liquibase/liquibase/pull/964/

That is a big one, and it appears to alter behavior as well as documentation, so it might take me a while to get it reviewed and merged. 

Steve Donie
Principal Software Engineer
Liquibase Community Engagement
Datical, Inc. http://www.datical.com/

3

Hi,

I’m trying to contribute in the documentation also. If I understand correctly to change the documentation of a change like loadData then the steps are:

  1. Clone the liquibase repository
  2. Change the description value of the repository?
  3. Or the *.htmls shall be also generated further from the *.md files some way and committed?
  • Or it is done by some CI step? If not, shall the bundle used for that?

What are the steps for other changes like changing documentation\changeset.md?

Thanks,

    Gyula Bibernáth