Files
gitlabhq/doc
Jacob Schatz 37707ac59e Merge branch 'css-style-guide' into 'master'
CSS style guide

Working towards what was discussed in #13552, this adds the [SCSS Linter gem](https://github.com/brigade/scss-lint) for style guide conformity in CI.

TODO:
- [x] Agree on and write SCSS Style Guide Documentation.
- [x] Document the `scss-lint` config file.
- [x] Figure out how best to run this in CI, right now it's taking longer than I would think it should.
- [x] Use CSSComb for auto-correction (Maybe just include a CSSComb config file and have developers run the node package manually if they're interested in using it?).

My logic for not using CSSComb in the first place is that, AFAIK, we don't currently require Node/NPM, even in the dev environment. Maybe I'm wrong about that? `scss-lint` is a Ruby implementation of a similar concept, but it doesn't include autocorrect.

Is there a way we can run get GitLab CI to run `scss-lint` without having to put together the full GitLab application? Seeing as it's just static analysis, it seems like a waste of time/resources.

/cc @jschatz1 @rspeicher

See merge request !3069
2016-03-15 16:52:53 +00:00
..
2016-03-15 16:13:49 +00:00
2016-03-10 14:48:29 -05:00
2016-03-11 11:47:34 -05:00
2016-03-10 16:12:50 -03:00
2016-03-10 14:48:29 -05:00
2016-01-12 14:47:55 +01:00
2016-03-10 14:48:29 -05:00
2016-02-06 12:17:12 +00:00
2016-03-10 14:48:29 -05:00

Documentation

User documentation

CI User documentation

CI Examples

CI Services

GitLab CI uses the services keyword to define what docker containers should be linked with your base image. Below is a list of examples you may use:

Administrator documentation

Contributor documentation

  • Documentation styleguide Use this styleguide if you are contributing to documentation.
  • Development Explains the architecture and the guidelines for shell commands.
  • Legal Contributor license agreements.
  • Release How to make the monthly and security releases.