Not entirely sure if this is an appropriate place for this question but I'd like to get my pull requests to show the status of the CircleCI build but can't find any solid documentation on it. The two are integrated and the builds start running as soon as a PR is created. I found some docs that said I should go to Settings > Branches and then request that status checks pass before merging, but there are no options for CircleCI listed. Am I missing something obvious?
CircleCI Discuss would be the best place but I can try to answer here.
My first suggestion would be to redo the webhooks. By unfollowing and refollowing the project. This isn't the same issue but troubleshooting steps would be similar to: https://circleci.com/docs/2.0/workflows-waiting-status/
Related
I have this issue when I try to merge my branch to the main one for my RASA chatbot project and I want to know if there are any ways to fix this and create a pull request or should I just change my main branch to the domain-side branch
Ok so I fixed the issue by deleting the .rasa cache folder
This can occur when there are a lot of commits in your Pull Request
Unfortunately, this is a known github issue.
Thanks for writing to GitHub support and sorry for the trouble!
We have received a few similar reports regarding big pull requests. I can confirm that our team is working on fixing this problem, and I've added your report to that issue.
Unfortunately I won't be able to provide an estimated time on when this might get fixed. We know this is not ideal, but hope you understand.
Is there anything we can do to preserve our comments and alleviate this issue now and in the future?
You should be able to use our API to get a copy of the comments in this pull request:
https://developer.github.com/v3/pulls/comments/#list-comments-on-a-pull-request
https://developer.github.com/v3/pulls/reviews/#list-reviews-on-a-pull-request
If you have any question regarding using API we can definitely offer more detailed instructions.
Unfortunately I'm not sure if there's anything you can do on your part to view this pull request normally.
One thing you could try is viewing this PR in Incognito window or logged out.
I was actually able to view the PR you linked because I don't have write access to this repository, so GitHub will try to load less things for me such as edit buttons and so on. Of course this won't allow you to merge the pull request and so on, but perhaps it would help for you to look at its content?
Lastly, while we are working on consistently supporting large pull requests, you might consider keeping pull requests relatively short for now to avoid running into this again.
I hope this helps clear things up, and please let us know if you have any other questions.
Please refer to the full discussion provided here.
I can't share any screenshots for proprietary reasons, but has the re-run button for GitHub checks been removed? It used to be that you could click "Checks" on a pull request, and there would be a button that you could press to trigger a webhook specifying this run should be done again.
Is this a problem on my end, or has this feature been removed? As far as I can tell, it just disappeared at some point. The documentation for GitHub checks is remarkably sparse and vague, I'm having a hard time figuring out what to do.
If you are talking about GitHub Enterprise, it might depends on its version.
But a GitHub check, from its documentation offer rerun for failed checks.
So:
either those checks are not failed
or there is a permission issue which would make your profile unable to access the rerun feature (check with your GitHub Enterprise admin)
I am currently working on the CI of project and I deploy a preview for each github branch that pass all integration tests.
My CI workflow is executed by CircleCI and I can see the progression on github with Github checks. It works pretty nice but description does not reflect what really happens.
For instance I can see this on github :
My problem is I would like to custom message and details actions link. My last job deploys a preview and I would like to be able to put the link somewhere. The best case should be able to open my preview when I click on details button.
Is there any way to do this ?
I send a mail to CircleCI support and I got this anwser :
Hello,
It is not possible at this time to customize this text. Clicking the
details link will bring you to the job on CircleCI. We are currently
working on a utility that will allow you to post comments to the PR
from within a job that may be close to what you are looking for. This
will exist in an Orb (https://circleci.com/orbs/registry/) but I could
not say exactly how long until this is released, though we are
actively working on it.
You may wish to post to our public facing ideas portal:
https://ideas.circleci.com/ideas as a new idea post. This will let our
community vote for this request. Please let us know if we can assist
any further.
So, unfortunately it is not possible yet. Maybe in the future.
it is a bad way to do code reviews after pull request has been initiated. sometimes we want to do code reviews before the whole thing is ready for integration. is there any tools out there that will allow code review without pull request? I prefer cloud based solution such as reviewable but it only works with pull request...
Fastforward to 2019. Github now offers "draft pull requests":
https://github.blog/2019-02-14-introducing-draft-pull-requests/
WIP (Work in Progress) pull requests are pretty common. GitHub doesn't have a built-in feature like GitLab or Gerrit have, but it's pretty easy to just do this by consensus: Open a PR that's prefixed with WIP: to indicate it isn't ready for being merged, but is open to feedback, and keep updating it (with git push --force most probably) as you go. Once you're done, you can remove the WIP: prefix.
EDIT:
While it isn't a built-in feature, the WIP third party app seems to help automate this for you, and prevent you from merging a WIP branch by mistake.
It would be really great to have a Github issue be in an intermediary "Resolved" state before I close the issue.
Right now, I have a "Resolved" label and I manually select the issue and change it's label on the web after I commit. Is there a way I can do this from the commit message?
I am sure this is a common problem. How do you guys solve this?
I have never used Github API but can this be done using the API If I were to do this myself?
Since September 14, 2016 you could manage your states with projects. See image below:
Reference and source: GitHub - A whole new GitHub Universe: announcing new tools, forums, and features.
I know it's not like a new state like "needs verification" because you can't like #NevikRehnel said in his answer. But you could make a column named "open", "needs verification" and "closed" and all the issues can you list in correct column.
No, Github issues only support two states (open and closed). Any other "states" must be realized via labels, as you are already doing right now.
And as of right now, there is no way to apply labels from commit messages.
You can always request such features from Github support of course, and they might be implemented at some point.
You can manage this problem using this method : Adding and reassigning github issues via commit message.
A simple ruby script will run on each commit, and check the commit message looking for ~myLabel and =assignedMember to update correctly the issue.