I made a lot of pull request, and some of them were approved disapproved by some reviewers.
How do I delete the history of my reviewers so they will not be suggested again under 'Recent'?
Bitbucket hasn't implemented a way to clear the Recent reviewers list yet. Their only suggested option is to change the 'Default Reviewers' of the project.
Related
I would like to know if it is possible to add and remove users (by email) from the list of authorized external users for testflight.
If so, where can I find documentation on how to do that?
Not manually, but automated.
The app store connect API can create and delete beta testers (i.e., Testflight users). You should study that documentation first, then come back with more questions if there are things you don't understand.
I have a tool that automatically adds reviewers to a Gerrit review. I don't want to add reviewers for draft reviews (created with: git push origin HEAD:refs/drafts/master). I have not been able to figure out how to conclude if a review is a draft or not. The Gerrit patchset-created events contains no such info.
What is the best way conclude if a certain review is draft or not?
If your Gerrit version is 2.14.x or below:
Look at the IS_DRAFT parameter, which will receive the true (draft) or false (not draft) value.
We have users on Phabricator who are being migrated over to Bitbucket.
They have come to prefer the following behavior:
The engineer who created a pull request would not be notified of any review feedback until the reviewer performs "submit" or "publish". This allows the reviewer the time to write and revise their feedback as they read the code and begin to understand the entirety of the change set.
In the Bitbucket world, the reviewer's feedback gets sent (by default) as soon as he or she hits "Comment" the change set/pull request creator gets notified.
Is it possible, via plugin or settings change, to get Bitbucket to hold off on the notification bit until the reviewer is ready?
We are using gerrit for our project. We have a jenkins job to run compile and test, then it give a verification score.
After I push a patch set, the jenkins job starts to run and reviewers start to review code. But the job may failed while the reviewers are doing code review. So is it possible that a jenkins job verification process before code review.
In other word, reviewers receive code review notification only after verification is passed
If it's not enough just to ask the reviewers to hold their reviews until the patch set is verified, and you really need to hide a code review until it has ben successfully built by Jenkins, you can make use of Drafts:
configure Jenkins to kick off a build when a Draft is published
publish your code review as a Draft
add Jenkins as a Reviewer when you push so it can see the draft being published
when the build succeeds, publish your draft for the reviewers to see
I am trying to add new users to my Users and Roles in iTune Connect. I go through the steps, assigning them as Technical/Admin, and hit the Add button.
I get the confirmation on the dashboard that they have been sent a verification email... but it seems nothing is being sent!! And as a result I cannot add them to the Internal testers list.
Is there a reason why verification emails are not being sent to new users being added?
Cheer
AF
iTC TestFlight has been notorious for dropping emails. Apple has also been having outages recently related to iTC (as well as other systems). The only thing you can do is remove the user and later re-add them - that will trigger the invite email again, and if iTC is working properly at the time they'll get the email.
You might also want to reach out to support so they can see if there is anything going on with your account. I had to do this for an iTC issue last week...and I heard back a week later that the issue was resolved.
Good luck!