Here are my repo settings:
So I expect notifications only if something changes. But it continues to inform me of the following letters:
"Coverage remained the same at 100.0% when pulling [commit-hash] on dev into [commit-hash] on master."
How to fix it?
Edit: I think this happens only with PRs. But anyway...
Yeah, I also use Travis CI, where Coveralls check triggers.
Oh! I got it, it is not Coveralls' notifications, it is GitHub notifications, which you can manage on 'Settings' page. These messages were sent because Coveralls left comments on PRs in repository I am watching.
Related
I cannot find an option to delete a PR on BitBucket.
Am I overlooking something or it's really not possible?
You can decline a pull request which has the same result -- stopping / removing the PR.
As per the link jonrsharpe mentioned, to the right of the merge button there are 3 dots. Under that menu you should have a delete option if you have permission to delete.
This is available only for BitBucket Server, not on BitBucket.org.
In BitBucket.org there is no option to delete the PR.
For Bitbucket Cloud, there are no way to do this. One way of getting by is to have a 'dev/junk' branch, used for declined or useless pull requests.
Then just edit the existing request to go into this branch and merge.
Data is still there, in case you need it some day, or if it's sensitive info you can remove the whole branch. If its already declined before, well, nothing can be done then other than recreating that repo
See https://jira.atlassian.com/browse/BCLOUD-8089 for the update on this feature request and vote on it!
I wanted to delete a pull request of a branch that had already been merged and deleted. Even though I am an admin of my project, I cannot see any "delete" options. For me what worked was to recreate the deleted branch from the main branch and push it. E.g.
git checkout master
git checkout -b [deleted branch name]
git push -u origin [deleted branch name]
Then I opened Bitbucket and the branch showed up as "merged" and disappeared from the PRs list.
You cannot delete the PR in bitbucket.org .
Using Decline option will do exactly what you want - the PR won't be visible in the tab Pull requests (you need to sort PR by Decline to see it) but on tab Branches you will see that in column Pull request you have removed your problematic PR.
PS you cannot undo Decline of PR, so take care
I have a travis.yml script as part of a package on my github site. So every time I push an update, it is automatically rebuilt and checked. However, sometimes I know it won't build correctly and I am just pushing my changes to keep from losing them.
Another incentive for suspending a build is that I literally cringe when I receive an e-mail with a subject line saying it has "errored." I wish somebody would tell this Travis guy that "error" is a noun, not a verb.
The best way to handle your travis build would be to setup a branch where the build is trigger and to build in another branch. This way, you will do what you want and only trigger the build when you will do a merge.
About the verb errored, it isn't currently a verb. But it will maybe be, like to google.
error (third-person singular simple present errors, present participle erroring, simple past and past participle errored)
(computing) To function improperly due to an error, especially accompanied by error message.
The web-page took a long time to load and errored out.
Remove that line of code and the script should stop erroring there.
This directory errors with a "Permission denied" message.
How can I enable auto fork syncing on BitBucket cloud ? I cant find the option and have to manually keep the fork updated.
Thanks!
While originally I found this article, it seems this only applies to their server product: https://confluence.atlassian.com/bitbucketserver/keeping-forks-synchronized-776639961.html
This article indicates that its a process you will need to manage manually on local:
https://confluence.atlassian.com/bitbucket/forking-a-repository-221449527.html
After you fork a repository, the original repository is likely to continue to evolve as other users commit changes to it. These changes do not appear in your fork. However, you can pull these changes into your fork later by syncing changes locally from the command line.
While this describes pulling upstream manually, you could probably script something to do this more automatically for your purposes. If I end up doing something like this for our team, I'll update this answer with more details or perhaps someone else will do the same.
I have a Ruby/Rails project I inherited. It's a private github repo, and it's hooked up to CircleCI in the standard way: github won't allow a merge til the required CircleCI tests pass. That's fine, but when I create a pull request, I only get "ci/circleci — Waiting for status to be reported" and that never changes (I waited all weekend). I'm not sure where to look for log files, or what might be going wrong. I'm new to CircleCI. Any help? The last item I see in my circleci dashboard is months ago, so it's almost like it's not seeing the new pull request. But I can see github sending it and getting a 200 reply.
BTW, the circle.yml just sets the machine timezone, nothing else, nothing fancy.
You may need to configure the branch settings:
https://circleci.com/docs/2.0/workflows-waiting-status/
I setup travis-ci for a new rails project, but for some reason the build status is always shown as unknown in my README. I have googled a bit and not been able to find any solutions. Although I have had some similar symptoms as others. E.g., all of my builds show they are still building, but if you look at the individual builds they are passed or failed.
BTW, should this be reported as a travis-ci issue?
I ran in to the same issue. I was able to address the issue by adding the branch parameter to the image url:
This url did not work
https://travis-ci.org/kandadaboggu/iprofiler.png
This url worked
https://travis-ci.org/kandadaboggu/iprofiler.png?branch=master
.com will not work here, as per latest. This works for me
## Travis-Build
[](https://travis-ci.org/sananand007/genTspsolver)
Travis-Build
I use the Travis badge in our project's README in Github and I had the same issue. It turned out I did not have the correct settings in Travis.
From your Travis dashboard, go to More options => Settings. For me, I needed to turn on "Build pushed branches." After that, I clicked More options => Trigger build, and triggered a build.
Once Travis ran (and passed), I went back to Github and hard refreshed the page. The Travis badge had updated to green, or "build: passing".
In my case, the links I used were based on travis-ci.org when as of May 2018, all links should use travis-ci.com
See this announcement
This registered unknown
https://travis-ci.org/jlboat/FastaUtils.png?branch=master
This registered passing
https://travis-ci.com/jlboat/FastaUtils.png?branch=master
My issue was just that I this was my first build on travis-ci.org after I made my app public instead of private. I just had to wait for the image to be updated to reflect the new build status, which took a couple minutes. It is a free service on the .org rather than the paid service on the travis-ci.com so we have to wait on the shared resources to create the build status image.
In my case, the issue resolved by opening the image url on browser. You can get the image url from the Status Image popup by clicking build status badge on your project dashboard. The build status changed immediately after the image url fully loaded on the browser. For example click me
Follow a simple rule: use link of your travis repository dashboard.
In my case it's https://travis-ci.com/<username>/<repository>