The linters branch is going to contain all configs for linting and then will be eventually merged into master when it's ready. For now this MR will be used to discuss all code style and linting related questions.
The `linters` branch is going to contain all configs for linting and then will be eventually merged into master when it's ready. For now this MR will be used to discuss all code style and linting related questions.
I think we should only lint code from this repo/project; the quality of included code (patek-logo-element for example) is to be taken care of in their projects. I would probably solve it somehow generally e.g. putting external code to external subfolder and exclude it from the linting pattern.
Thanks for your contribution.
I think we should only lint code from this repo/project; the quality of included code (patek-logo-element for example) is to be taken care of in their projects. I would probably solve it somehow generally e.g. putting external code to `external` subfolder and exclude it from the linting pattern.
added 1 commit
<ul><li>69c9a96d - Added an html linter. It doesn't produce any errors. Either the code is...</li></ul>
[Compare with previous version](/patek-devs/patek.cz/merge_requests/1/diffs?diff_id=48701110&start_sha=8f88e54299793856435f76e02a92ac0d2f3562d8)
added 3 commits
<ul><li>c63825bf - Enable Gitlab CI to test buildability.</li><li>7cbcef39 - Merge branch 'vojta001/gitlab-ci' of gitlab.com:patek-devs/patek.cz into linters</li><li>cb062f0b - Added linting to .gitlab-ci.yml</li></ul>
[Compare with previous version](/patek-devs/patek.cz/merge_requests/1/diffs?diff_id=48707865&start_sha=e6f64ef997ce364766b7d5f879b0753d23d51ae8)
But it can be used separately as well and getting linting results in job logs of this project is of little value for the development and maintenance of the logo itself.
And then there is Bulma...
But it can be used separately as well and getting linting results in job logs of this project is of little value for the development and maintenance of the logo itself.
And then there is Bulma...
added 1 commit
<ul><li>c97bbb18 - Added Makefile for local linting and checking.</li></ul>
[Compare with previous version](/patek-devs/patek.cz/merge_requests/1/diffs?diff_id=48716535&start_sha=0ca34bb9f52237dd10c8a4984220876a38eb7e10)
I think we can slowly move to merging this to master. Are you OK with me doing some polishing by rewriting your carefully written history? The same applies for !2 especially since these two are connected so much
I think we can slowly move to merging this to `master`. Are you OK with me doing some polishing by rewriting your carefully written history? The same applies for !2 especially since these two are connected so much
Well, you could merge just firebase-deploy, since that already contains all changes. Also, didn't we talk about putting deployment/building/production related stuff into a separate branch? Yea, a cleanup of the history would be nice.
Well, you could merge just firebase-deploy, since that already contains all changes. Also, didn't we talk about putting deployment/building/production related stuff into a separate branch? Yea, a cleanup of the history would be nice.
added 6 commits
<ul><li>1802ae01 - Added js linter config.</li><li>53147093 - Added an html linter. It doesn't produce any errors. Either the code is...</li><li>5ed936d5 - Added sass linting.</li><li>99aa6da0 - Merge branch 'vojta001/gitlab-ci' of gitlab.com:patek-devs/patek.cz into linters</li><li>8331f0a7 - Added linting to .gitlab-ci.yml</li><li>111761f8 - Added Makefile for local linting and checking.</li></ul>
[Compare with previous version](/patek-devs/patek.cz/merge_requests/1/diffs?diff_id=48986691&start_sha=c97bbb184e802755bb4a025ab6af32b18f2b12a3)
I think we should finish the master/production and CI/CD discussion and whether to lint external code discussion before merging.
I've finally done the cleanup.
I think we should finish the *`master`/`production` and CI/CD* discussion and *whether to lint external code* discussion before merging.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The
lintersbranch is going to contain all configs for linting and then will be eventually merged into master when it's ready. For now this MR will be used to discuss all code style and linting related questions.added 1 commit
95b1c701- WIP.Compare with previous version
assigned to @sijisu and unassigned @Greenscreener
assigned to @vojta001 and unassigned @sijisu
assigned to @Greenscreener and unassigned @vojta001
added 2 commits
94462d17- 1 commit from branchmaster8f88e542- Merge branch 'master' into lintersCompare with previous version
Thanks for your contribution.
I think we should only lint code from this repo/project; the quality of included code (patek-logo-element for example) is to be taken care of in their projects. I would probably solve it somehow generally e.g. putting external code to
externalsubfolder and exclude it from the linting pattern.While I agree, IMHO patek-logo can be linted too as it's developed alongside this project.
added 1 commit
69c9a96d- Added an html linter. It doesn't produce any errors. Either the code is...Compare with previous version
added 1 commit
e6f64ef9- Added sass linting.Compare with previous version
unmarked as a Work In Progress
I think we're essentially ready for merge if you guys agree.
Since I don't think GitLab has review requests as of yet, I'll just tag @sijisu and @vojta001.
added 3 commits
c63825bf- Enable Gitlab CI to test buildability.7cbcef39- Merge branch 'vojta001/gitlab-ci' of gitlab.com:patek-devs/patek.cz into linterscb062f0b- Added linting to .gitlab-ci.ymlCompare with previous version
added 1 commit
a0a8f355- Fixed typo.Compare with previous version
added 1 commit
1783ad93- WIPCompare with previous version
marked as a Work In Progress from
1783ad9306added 1 commit
5fc314e7- WIPCompare with previous version
But it can be used separately as well and getting linting results in job logs of this project is of little value for the development and maintenance of the logo itself.
And then there is Bulma...
Yes, bulma is ignored, because it uses sass files and we lint only scss.
added 1 commit
0ca34bb9- Ah bollocks...Compare with previous version
unmarked as a Work In Progress
added 1 commit
c97bbb18- Added Makefile for local linting and checking.Compare with previous version
unassigned @Greenscreener
I think we can slowly move to merging this to
master. Are you OK with me doing some polishing by rewriting your carefully written history? The same applies for !2 especially since these two are connected so muchWell, you could merge just firebase-deploy, since that already contains all changes. Also, didn't we talk about putting deployment/building/production related stuff into a separate branch? Yea, a cleanup of the history would be nice.
added 6 commits
1802ae01- Added js linter config.53147093- Added an html linter. It doesn't produce any errors. Either the code is...5ed936d5- Added sass linting.99aa6da0- Merge branch 'vojta001/gitlab-ci' of gitlab.com:patek-devs/patek.cz into linters8331f0a7- Added linting to .gitlab-ci.yml111761f8- Added Makefile for local linting and checking.Compare with previous version
I've finally done the cleanup.
I think we should finish the
master/productionand CI/CD discussion and whether to lint external code discussion before merging.We should probably merge the last commit from master, since it has code style updates relevant for this branch and the lint jobs will fail.
We decided to make the two branches identical, the only difference is that deploy and build happen only on production.
merged
mentioned in commit
3fb47992db