-
Notifications
You must be signed in to change notification settings - Fork 223
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
README.md: Remove Spacing Inconsistency #724
Conversation
Travis tests have failedHey @sladyn98, Ruby: 2.5.1docker run -v=$(pwd):/app --workdir=/app coala/base coala --ci
TravisBuddy Request Identifier: 961d0580-4ef1-11e9-af0a-1da2f5ed2a53 |
Travis tests have failedHey @sladyn98, TravisBuddy Request Identifier: 03551620-4ef6-11e9-af0a-1da2f5ed2a53 |
Travis tests have failedHey @sladyn98, TravisBuddy Request Identifier: 107fcb50-4ef7-11e9-af0a-1da2f5ed2a53 |
Travis tests have failedHey @sladyn98, TravisBuddy Request Identifier: 08778fa0-4ef8-11e9-af0a-1da2f5ed2a53 |
Hey @sladyn98, TravisCI finished with status TravisBuddy Request Identifier: f1fcae10-4efa-11e9-af0a-1da2f5ed2a53 |
Hey @sladyn98, TravisCI finished with status TravisBuddy Request Identifier: e60277b0-4efb-11e9-af0a-1da2f5ed2a53 |
Hey @sladyn98, TravisCI finished with status TravisBuddy Request Identifier: 063ca180-4efd-11e9-af0a-1da2f5ed2a53 |
Hey @sladyn98, TravisCI finished with status TravisBuddy Request Identifier: 907865e0-4efe-11e9-af0a-1da2f5ed2a53 |
Travis tests have failedHey @sladyn98, TravisBuddy Request Identifier: 76214670-4eff-11e9-af0a-1da2f5ed2a53 |
Travis tests have failedHey @sladyn98, TravisBuddy Request Identifier: e7e72e80-4f01-11e9-af0a-1da2f5ed2a53 |
Travis tests have failedHey @sladyn98, TravisBuddy Request Identifier: 79e14260-4f04-11e9-af0a-1da2f5ed2a53 |
Travis tests have failedHey @sladyn98, TravisBuddy Request Identifier: 7edacc90-4f05-11e9-af0a-1da2f5ed2a53 |
Travis tests have failedHey @sladyn98, TravisBuddy Request Identifier: 66b787a0-4f07-11e9-af0a-1da2f5ed2a53 |
.travis.yml
Outdated
@@ -22,6 +22,19 @@ jobs: | |||
cache: pip | |||
install: pip install moban | |||
script: .ci/check_moban.sh | |||
- stage: coala |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and this added?
These changes are not related to the SpaceConsistencyBear
issue afaik
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No your right these sections are not related. This is related to another issue #600. Actually makman2 and me were planning to fix the CI in this pr itself because gsoc is already upon us. I have discussed this with him and based on that appropriate action will be taken :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's great. Just add that issue reference to the comment/pr as well.
.travis.yml
Outdated
python: 3.6 | ||
cache: pip | ||
install: | ||
- cOALA_ZIP_URL=https://github.com/coala/coala/archive/master.zip |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- cOALA_ZIP_URL=https://github.com/coala/coala/archive/master.zip | |
- COALA_ZIP_URL=https://codeload.github.com/coala/coala/archive/master.zip |
@sladyn98 I would've really liked if there is a single PR fixing the CI. Two PRs for same purpose makes one redundant. Although this PR references changes regarding space consistency but the goal is same. Anyways, as soon as #600 is finished, you need to cherry pick that commit and push here. We should be able to see the CI green here, since that commit is has been done before than this (following linear git history). |
Yeah @abhishalya your bang on I will remove the changes from my PR once #600 has been fixed :) |
_reports/GuangyuanYang.md
Outdated
@@ -164,7 +164,7 @@ investigation/review. Based on this feature, I implemented a | |||
[script](https://gist.github.com/yzgyyang/13ebb46a5c90ac624b5c6eb43deedc0d) to | |||
demonstrate the ability of bootstrapping coala Go bears on a bare-metal FreeBSD | |||
system | |||
([Screen record for the demo](https://asciinema.org/a/0poVbHE7lqehV4islFo6cptjb)), | |||
([Screen record for the demo]()), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so this is required. This was reporting InvalidLink because we were using old coala. You should run latest coala and verify if it still throws InvalidLink.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just followed up on @kriti21's PR and I think she installed the latest coala and still the bear complained.
_projects/use-coala.md
Outdated
@@ -64,14 +64,14 @@ so that coala can check most file types. | |||
|
|||
Find a GitHub repository that meets all these criteria: | |||
|
|||
1. 100 or more [stars](https://help.github.com/articles/about-stars/), | |||
1. 100 or more [stars](https://help.github.com/articles/about-stars), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these changes related to SpaceConsistency?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No the link bear complained even after we installed the latest version so I removed the backslash
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then I think its better to add a new commit for this change. Actually for all invalid link changes.
@abhishalya @kriti21 https://travis-ci.org/sladyn98/projects/builds/511483343 I have linked the branch which made the CI green on my local fork you can have a look.The one problem is the asci link. I do not think I should have made that change because we just cannot remove a link from someone's project.So we need to find a workaround that. |
Travis tests have failedHey @sladyn98, TravisBuddy Request Identifier: 5088ccf0-52bd-11e9-b3ee-317c5c727117 |
Travis tests have failedHey @sladyn98, TravisBuddy Request Identifier: a44a2fe0-52be-11e9-b3ee-317c5c727117 |
Readme.md contained some spacing inconsitency which has been now removed. Fixes #713
Travis tests have failedHey @sladyn98, Ruby: 2.5.1docker run -v=$(pwd):/app --workdir=/app coala/base coala --ci
TravisBuddy Request Identifier: fc0746f0-52be-11e9-b3ee-317c5c727117 |
Travis tests have failedHey @sladyn98, Ruby: 2.5.1docker run -v=$(pwd):/app --workdir=/app coala/base coala --ci
TravisBuddy Request Identifier: 260d5570-52bf-11e9-b3ee-317c5c727117 |
Travis tests have failedHey @sladyn98, Ruby: 2.5.1docker run -v=$(pwd):/app --workdir=/app coala/base coala --ci
TravisBuddy Request Identifier: 5edb6ae0-52bf-11e9-b3ee-317c5c727117 |
Travis tests have failedHey @sladyn98, Ruby: 2.5.1docker run -v=$(pwd):/app --workdir=/app coala/base coala --ci
TravisBuddy Request Identifier: 7dfe9be0-52bf-11e9-b3ee-317c5c727117 |
Travis tests have failedHey @sladyn98, Ruby: 2.5.1docker run -v=$(pwd):/app --workdir=/app coala/base coala --ci
TravisBuddy Request Identifier: 150c3bc0-9b6b-11e9-82c9-337585006a18 |
@jayvdb This fixes the spacing inconsistency and is ready to be merged IMO. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need a correct rebase (2nd commit in ur changes shouldn't be there)!
Duplicate of #600 |
Readme.md contained some spacing inconsitency
which has been now removed.
Fixes #713
For short term contributors: we understand that getting your commits well
defined like we require is a hard task and takes some learning. If you
look to help without wanting to contribute long term there's no need
for you to learn this. Just drop us a message and we'll take care of brushing
up your stuff for merge!
Checklist
them.
individually. It is not sufficient to have "fixup commits" on your PR,
our bot will still report the issues for the previous commit.) You will
likely receive a lot of bot comments and build failures if coala does not
pass on every single commit!
After you submit your pull request, DO NOT click the 'Update Branch' button.
When asked for a rebase, consult coala.io/rebase
instead.
Please consider helping us by reviewing other peoples pull requests as well:
cobot mark wip <URL>
to get it outof the review queue.
The more you review, the more your score will grow at coala.io and we will
review your PRs faster!