Closed sladyn98 closed 5 years ago
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @sladyn98, Something went wrong with the build.
TravisCI finished with status errored
, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.
Hey @sladyn98, Something went wrong with the build.
TravisCI finished with status errored
, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.
Hey @sladyn98, Something went wrong with the build.
TravisCI finished with status errored
, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.
Hey @sladyn98, Something went wrong with the build.
TravisCI finished with status errored
, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
@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 https://github.com/coala/projects/pull/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).
@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 :)
@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.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
Hey @sladyn98, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.
@jayvdb This fixes the spacing inconsistency and is ready to be merged IMO.
Duplicate of #600
Readme.md contained some spacing inconsitency which has been now removed.
Fixes https://github.com/coala/projects/issues/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
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 out of the review queue.The more you review, the more your score will grow at coala.io and we will review your PRs faster!