VS/Git: How to create a notification (alert?) / View History whenever code in a specific solution goes to a Pull Request (PR)
Hi All
I'm running Visual Studio Pro 2017, and have access to about 100+ solutions for SQL Server databases we have here. I'm assigned to teams that are heavy users to two specific solution/databases, and am expected to speak to any database change for those databases.
Question: How can I either...
1 Do a View History on an entire solution? In TFS I could do this by clicking on the Solution file and then right-click > View History, but in Git this only works for the solution file itself and not the entire solution.
2 Create a notification (alert?) that sends an email anytime anybody makes a change to a specific solution, and then creates a Pull Request (PR) on it? Going into User Settings > New Subscription, it only allows me to differentiate by branch, and not by solution.
Thanks in advance.
Jim
I'm running Visual Studio Pro 2017, and have access to about 100+ solutions for SQL Server databases we have here. I'm assigned to teams that are heavy users to two specific solution/databases, and am expected to speak to any database change for those databases.
Question: How can I either...
1 Do a View History on an entire solution? In TFS I could do this by clicking on the Solution file and then right-click > View History, but in Git this only works for the solution file itself and not the entire solution.
2 Create a notification (alert?) that sends an email anytime anybody makes a change to a specific solution, and then creates a Pull Request (PR) on it? Going into User Settings > New Subscription, it only allows me to differentiate by branch, and not by solution.
Thanks in advance.
Jim
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
np. I'm a Git N00b as my previous ten-ish years was all TFS, so this is a pretty decent learning curve.
ASKER
Cleaning up older questions, and I've since left this employer and no longer work in a Git shop, so marking as the answer.
ASKER