Skip to content
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

.coafile: Ignore coala in generated GCI files #52

Merged
merged 1 commit into from
Dec 17, 2017

Conversation

jayvdb
Copy link
Member

@jayvdb jayvdb commented Dec 17, 2017

The GCI exported data contains 'coala',
so it needs to be excluded from the relevant checks.

Also ignore private/** and delete it regularly,
as a preventative measure for accidental leaks.

Related to #3

The GCI exported data contains 'coala',
so it needs to be excluded from the relevant checks.

Also ignore private/** and delete it regularly,
as a preventative measure for accidental leaks.

Related to coala#3
@@ -7,6 +7,7 @@ mkdir private _site public
if [[ -n "$GCI_TOKEN" ]]; then
python manage.py fetch_gci_task_data private
python manage.py cleanse_gci_task_data private _site
rm -rf private/
Copy link
Member

Choose a reason for hiding this comment

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

What's up with this?

Copy link
Member Author

Choose a reason for hiding this comment

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

The private data collected on line 8 has been cleansed and pushed into _site , and is no longer needed. It is what is causing the coala errors. This is the first place to remove it.

@@ -12,6 +12,7 @@ before_install:

script:
- ./.ci/build.sh
- rm -rf private/
Copy link
Member

Choose a reason for hiding this comment

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

And this one as well...

Copy link
Member Author

Choose a reason for hiding this comment

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

and in case somehow the directory is still existing here, it should be removed. Extra careful.

@yukiisbored
Copy link
Member

ack 890cafa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants