8000 Improve markdown in comments for ``CI job started`` and ``build failed`` by DanielNoord · Pull Request #156 · channable/hoff · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Improve markdown in comments for CI job started and build failed #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

Closed
wants to merge 2 commits into from
Closed

Improve markdown in comments for CI job started and build failed #156

wants to merge 2 commits into from

Conversation

DanielNoord
Copy link

Closes #151

I ran into various issues trying to test this locally. For example, stack assumes nix is installed which wasn't listed as a requirement. (Note the If using Nix in the README).
Either way, since this is a fairly trivial markdown change I thought I would still submit the PR.

Let me know if this requires any changes 😄

@rudymatela
Copy link

@DanielNoord Thanks for the addition. 😄 Tests are passing here.

I will merge this myself later this week after I merge #137.

@rudymatela rudymatela added enhancement New feature or request good first issue Good for newcomers labels Aug 16, 2022
@rudymatela
Copy link

... I am "assigning" this to me so I don't forget to merge it later.

@DanielNoord I've marked you as an assignee as well, so you can have the clear credits when I merge (feel free to unnasign yourself if you rather it not appear under your main GH issues tab).

@rudymatela rudymatela mentioned this pull request Aug 16, 2022
43 tasks
@DanielNoord
Copy link
Author

... I am "assigning" this to me so I don't forget to merge it later.

@DanielNoord I've marked you as an assignee as well, so you can have the clear credits when I merge (feel free to unnasign yourself if you rather it not appear under your main GH issues tab).

Thanks! Wouldn't it show up anyway? My account should appear in the commit tree of the repo right?

@rudymatela
Copy link

@DanielNoord I've marked you as an assignee as well, so you can have the clear credits when I merge (feel free to unnasign yourself if you rather it not appear under your main GH issues tab).

Thanks! Wouldn't it show up anyway? My account should appear in the commit tree of the repo right?

You're right, it will. I just wanted to make the credits clearer. :-)

@rudymatela
Copy link

@OpsBotPrime merge on Friday

@OpsBotPrime
Copy link

Pull request approved for merge by @rudymatela, waiting for rebase behind 2 pull requests.

@OpsBotPrime
Copy link

Failed to rebase, please rebase manually using

git rebase --interactive --autosquash origin/master markdown-comment

@rudymatela
Copy link

@OpsBotPrime merge on Friday

@OpsBotPrime
Copy link

Pull request approved for merge by @rudymatela, rebasing now.

@OpsBotPrime
Copy link

Rebased as e02641f, waiting for CI …

OpsBotPrime added a commit that referenced this pull request Aug 19, 2022
…`build failed``

Approved-by: rudymatela
Auto-deploy: false
@OpsBotPrime
Copy link

CI job started.

@DanielNoord
Copy link
Author

@rudymatela Not sure if this due to the recent merge train change, but this PR seems to have been merged to main but hasn't been closed. Should I just close it?

@rudymatela
Copy link

@rudymatela Not sure if this due to the recent merge train change, but this PR seems to have been merged to main but hasn't been closed. Should I just close it?

I will close it now.

I don't think this is related to the merge trains change. Usually GitHub closes PRs automatically when they are merged into the main branch. In this case, it failed to detect that the branch was merged because it was from a different remote repository.

I think that this issue has always been present with Hoff... Perhaps when it detects the branch is from a different remote, it should post a comment stating that the PR has been merged but that it should be closed manually, or something else appropriate. I will create an issue soon when I have the time and link it here.

@rudymatela rudymatela closed this Aug 19, 2022
@rudymatela
Copy link

This is a merge train example. #160
(Never mind this comment. I am just gathering a list to analyse.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Comment about build failures with a markdown link
3 participants
0