Saturday fun 😀

Playing around with Github PRs for #MSDyn365BC apps can be additive. So for last days:
1. Add labels based on folder that has been changed
2. Add labels based on size
3. Blocked wrongly named PRs
4. Blocked if PR does not been approved to release
5. Add automatic reviewers

And another one to make a #MSDyn365BC apps build even easier in Github. The pull request name must be started with one of the below prefixes if not reject 😜

Finally had some moment to play around with Github Actions in our #MSDyn365BC product repository. Now the labels are assigned automatically based on size of the pull request and the extension that we are modifying

Not exactly :) in this you need to show collected errors later. But you are right you cannot show the Action when you collecting the errors. For that you need to use Recommended Actions in the Error Message Page.

Then I would also escalate that: Adding things to all RC also is not great idea - and moreover duplicate cues that are standard does not make sense. Also if I see Revenue Current Month 0 having sales this month in other cue with high number looks odd.

Small trivia about #msdyn365bc. Which from the below are related to Service Contracts and which one is not. 🤔