Skip to content

Use gitignore moban #40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 11, 2018
Merged

Use gitignore moban #40

merged 2 commits into from
Jun 11, 2018

Conversation

jayvdb
Copy link
Member

@jayvdb jayvdb commented Jun 5, 2018

.gitignore Outdated

# ember-try
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could pull in the .gitignore from https://github.com/ember-cli/ember-try , but it would be better to push that to https://github.com/github/gitignore

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jayvdb jayvdb force-pushed the moban branch 2 times, most recently from ed808f7 to cc7a7d6 Compare June 5, 2018 11:00
@jayvdb jayvdb removed the process/wip label Jun 6, 2018
[Ll]ib
[Ll]ib64
[Ll]ocal
[Ss]cripts
Copy link
Contributor

@bekicot bekicot Jun 7, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why we want to ignore this in a JS project?

Although I may never add Scripts directory, but it seems like other people have a valid usage for it. (e.g Custom build scripts)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consistency.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, I thought it is only required in python project.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is required in a python project, but it comes from the Global VirtualEnv file, which is among a long list of Global files which are being included so that all repos support all editors/OS/etc. https://gitlab.com/coala/mobans/merge_requests/27/diffs#5042e0fe174c9e90b403cf80175c9c8b18257fb1_0_3

Then if someone wants to add any more personally important gitignores, we can tell them to go upstream and then we will import them to all repos consistently.

# http://iamzed.com/2009/05/07/a-primer-on-virtualenv/
.Python
[Bb]in
[Ii]nclude
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

include This seems normal in a js project.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it a problem for this repo?

https://gitlab.com/coala/mobans/issues/34 is unrelated to this.
If there is a problematic rule, we override with a !rule

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I add an include directory and it will be missing in git status.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't git ignore should only ignore files that relevant to its project?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+targets:
+  - .gitignore: coala-gitignore.jj2

I thought it was because it is using coala-gitignore.jj2 which causing it include python specific project ignore to this project's .gitignore

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This repo is configured to use the node ignore list. Nothing to do with python.
'coala' in coala-ignore filename refers to coala org, not coala tool. These are all global rules for editors, and are all from github.com repos.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See coala/gh-board#50 which is about a real problem, and how to detect real problems.

@bekicot
Copy link
Contributor

bekicot commented Jun 7, 2018

@blazeu
I think we should wait for https://gitlab.com/coala/mobans/issues/34
as the generic coala gitignore is not proper for ember apps.

# Virtualenv
# http://iamzed.com/2009/05/07/a-primer-on-virtualenv/
.Python
[Bb]in
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bin also seems normal to include in the repository.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But not this repository, or any other coala repository, so we're ok to include it ... :/

@jayvdb jayvdb force-pushed the moban branch 2 times, most recently from 633e5f1 to fa53e08 Compare June 10, 2018 04:25
@jayvdb jayvdb mentioned this pull request Jun 10, 2018
@jayvdb jayvdb requested a review from blazeu June 10, 2018 05:45
Use custom Emberjs.gitignore as it doesnt
exist upstream in https://github.com/github/gitignore

Related to https://gitlab.com/coala/mobans/issues/31
Copy link
Member

@blazeu blazeu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The global before_script is still being ran making the moban job fail.

@jayvdb jayvdb merged commit abac8f0 into coala:master Jun 11, 2018
blazeu added a commit to blazeu/git-task-list that referenced this pull request Jun 11, 2018
jayvdb added a commit to jayvdb/gsoc-prep-tasks that referenced this pull request Jun 11, 2018
jayvdb added a commit to jayvdb/gsoc-prep-tasks that referenced this pull request Jun 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants