In VSTS (now Azure DevOps), multiple updates can be pushed to a pull request (PR). You can compare any update with its previous update, and you can compare a rolled-up view of all updates with the original code before any changes were made. But how do I compare two arbitrary, non-sequential updates?
My scenario is that a PR has had quite a bit of back-and-forth with a total of 8 updates pushed. I last reviewed update 5, but now 3 more updates exist. I don't want to review 6-5, 7-6, 8-7 or all updates, I just want to review 8-5. How do I do that?
A workaround (in the absence of any user interface to configure two non-sequential updates to be compared) is to edit the iteration=xxxand base=xxx query string parameters in the url, e.g.:
https://xxx.visualstudio.com/xxx/_git/xxx/pullrequest/123?iteration=8&base=5&_a=files
This updates the UI as shown below:
I discovered this because I received an automated email from VSTS notifying me about the latest pushed updates. The email included a "View pull request" button. I clicked the button which took me to the PR in VSTS (I think to the Overview section). There was a notification banner towards the top of the page with a link about comparing update 5 with update 8 which I had never seen before. This sounded promising, so I clicked the link and it took me to the Files section and showed the differences between update 5 and 8 which is exactly what I wanted!
However, subsequent visits to the page (or clicking the "View pull request" button in the email again) don't show that link again, and I can't find anywhere in the UI that lets me define the two updates to compare. So this seems like a one-time opportunity. Miss it, and it's gone forever. I'd still like to know if there's a way to define two non-sequential updates to be compared in the UI, however, the poor man's url hack is a viable workaround for now.
Related
when i check the application status history tab of New Business License application ,i got confused by the same statuses multiple times. When clicking the form only we came to know who returned/approved the form? Is there any way for the user to know from the history tab itself without clicking on the form
There is no other option as of formsflow.ai v4.0.4 to show what changes are modified in case of monitoring Application History.
It depends totally upon the workflow you design, how the applicationStatus changes across each stage of workflow. So if you are confused by multiple status happening at same time, you can redesign the workflow in such a way.
I recently discovered that you can create Milestones and Project Boards on Github repositories.
With project boards, you can place issues and pull requests and move them around the boards (Kanban).
But what is the purpose of having pull request inside boards ? Aren't pull request associated with issues ? Why would I place pull request inside board ?
UPDATE:
As user #BertrandMartel pointed out(read answer below), it's all about how you use issues and pull request. Since Github is home for Open Source Development, users of software could create an issue to report something, but developers can create pull request to do their work. Developers don't have to report an issue, they only create features. Same is applied for end users; they probably want to point out if something is missing or not working properly. They are not expected to work on a project(create pull request).
When you add a pull request or an issue to the project board, it means you create a reference to an Issue or a pull request. No modification is done to the Pull request, it just says that this card links back to that pull request
Also a pull request is not associated with an issue. In fact a pull request is a special type of issue (note that it has a number field which is incrementing like the issue number when you create one). A pull request may be linked to other issues
But what is the purpose of having pull request inside boards
You can assign notes to it and associate them with a kanban style card which can be moved between different columns. Each columns having different meaning in terms of project management for your team
The model is the following :
Project
ProjectColumn
ProjectCard
ProjectCardItem (may point to Issue or pull requests)
Here is a graphical representation from graphql voyager :
From About project board :
Project boards are made up of issues, pull requests, and notes that
are categorized as cards in columns of your choosing. You can drag and
drop or use keyboard shortcuts to reorder cards within a column, move
cards from column to column, and change the order of columns.
Project board cards contain relevant metadata for issues and pull
requests, like labels, assignees, the status, and who opened it. You
can view and make lightweight edits to issues and pull requests within
your project board by clicking on the issue or pull request's title.
When we are doing the customization of a work item type in VSTS. Do we also have the ability to track the history of the customization itself?
For example, we are trying to find out when the start date field was added to our customized Bug work item type.
A field was not there in a previous Increment but we noticed it recently. Just want to find out if there is a date captured somewhere that tells us when it was added or who may have added it?
Unfortunately we cannot get the information from VSTS for now. No date or history included from the retrieved process information via REST API.
However there's already a user voice submitted here to suggest the feature to add Activity Log to VSTS to track user accesses, you can go and vote it up or submit a new one to suggest the feature again to achieve that is future release.
For now as a workaround we suggest that you can ask the team members to add corresponding comments in description area after completing the customization for the process... Thus you can track the history of the customization...
We're looking for a solution on how to best deal with the situation where multiple authors are working on the same page. If the first author pushes in the content, the second should have a way to merge it when he tries to publish. Launches appears to be a way to take care of this but it doesn't seem to be handling content merging. Is there any way an author can view the diff(and or do merge) of the content that might have been pushed by another author while they were working concurrently ?
Please help with any pointers.
Page modifications happen in real time to the underlying structure. They also happen at as small a level as possible.i.e. If you go into a text area and modify the text there, the text node is changed on the server, you aren't saving the entire page.
The only way that person A could interfere with what person B is doing is if they were working on the exact same area of the page. Which, honestly is a process issue. I say this because the answer to your question is that there is nothing out of the box to handle this type of scenario and if you are on 6.0 or higher and looking at the JCR3. JCR3 handles this far worse than the older version did. Last time I checked it didn't support nodes at all
Adding to what Bailey said, AEM OOB allow multiple users to edit same page in real time, though if multiple users are working on same node will be a reason of conflict. Such cases can be managed by defining a process like:
1. Take a lock of page and edit page or
2. Create versions of page and publish versions
I'm reading this google guide and using this sample code provided by google, but there's a glitch: using the back/forth buttons makes the URL change before the confirmation dialog has returned. This means that if the user decides not to navigate away, the URL no longer represents the current Place.
Anyone have a solution or workaround? Ideally, the URL would not change until the confirmation is given, but even just switching the URL back in a hurry after a denial would be better.
There's no workaround. Your app somehow detects that the URL has changed, which triggers the place change (thus before navigation is confirmed).
And there's no way to know why the URL changed; was it a "back"? a "forth"? a "back" using the history menu to go several steps back at a time? a bookmark? manual editing of the URL? So there's no way you could do a History.next() to "cancel" the URL change in all cases (also note that it would trigger another place change). And trying to modify the URL with anything else than History.back/next/go would erase the forward history, which you probably don't want either.
FYI, I implemented that behavior 2 years ago in my own "place manager", and talked about it with Ray Ryan when he added the PlaceHistoryHandler to GWT 2.1, and we agreed that there was no better behavior than letting the URL no longer being in sync with the place. FYI, when I studied the thing 2 years ago, and then earlier this year, GMail had the same behavior (create a draft message and navigate while the draft has unsaved changes).