-
Notifications
You must be signed in to change notification settings - Fork 156
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
#950 Updated How Rultor Works #991
Conversation
@gumbelmj Thanks for your pull request, let me find someone who can review it |
@caarlos0 review this please |
<li>Reports back to you, in the GitHub pull request.</li> | ||
</ol> | ||
You can see it in action, for example, in this pull request: | ||
<a href="https://github.com/jcabi/jcabi-github/pull/878">jcabi/jcabi-github#878</a>. |
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.
@gumbelmj this is a markdown file, please, use markdown syntax.
@gumbelmj please see my comment above |
I updated the pull request, but even MORE tests failed? Is that my issue? And if so, what's wrong? |
@gumbelmj thanks! |
@rultor merge |
@yegor256 ping |
@rultor merge |
@gumbelmj @yegor256 Oops, I failed. You can see the full log here (spent 2min)
|
@rultor merge |
@gumbelmj @yegor256 Oops, I failed. You can see the full log here (spent 15min)
|
@@ -26,15 +26,27 @@ TBD... _product statement_ | |||
|
|||
## What Problem Does Rultor Solve? | |||
|
|||
TBD... _stakeholders and needs_ | |||
TBD... _stakeholders and need |
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.
@gumbelmj you are missing the closing _
at the end of the line here...
@caarlos0 Doh! I missed that it even changed. Thanks. I fixed it. |
@yegor256 can we try again? |
@rultor try to merge |
Closes #997 Also pluralized "Problem" as Rultor solves more than a single problem. Wrote paragraphs instead of a enumeration so that the README looks more like thorough documentation and less like a TODO list.
…delimited by comma, by using regex for #821
…e mention being preceeded by a comma for #821
@yegor256 rultor is strange here... it says it merged the pull, but looks like it didn't |
@gumbelmj merge conflicts |
* Created new ShellCommand class to encapsulated running a command in a shell * Used ShellCommand to make EndsDaemon use fewer objects and remove duplicate logic for sanitizing and running commands in EndsDaemon
@caarlos0 I believe I fixed the merge conflicts. |
@rultor merge |
@gumbelmj @caarlos0 even though the team file is not yet updated, but by the power vested in me ... This should not be merged! The ticket asks for the readme file to be updated, this PR changes 14 files and would break the build anyhow and not pass(messes up the Jekyll gemset). |
@original-brownbear makes sense, seems like a wrong merge... |
@caarlos0 I'm closing this pull request and I will open a new one to resolve this issue. |
@caarlos0 10 mins added to @original-brownbear account (our architect), payment ID is |
Updated the Readme. Some checks failed. Do I need to be concerned about these?