Git (helpful)

Edit Answers
12345678910111213141516171819202122232425262728
Across
  1. 5. utility used to inject unique identifiers known as “tags” within source code, primarily for logging and telemetry feeds
  2. 8. responsible for the migration of changes across Git and SD
  3. 9. when creating a pull request, you’ll usually be merging a ___branch into an officialbranch
  4. 10. also known as Clippy for Pull Requests;____ is a tool account that has built in helpful routines for ensuring pull request health
  5. 12. a dangerous Git command, especially when using long-lived branches (like Office does); ideally you use <git backout> instead
  6. 13. <scoper ___> will allow you to view the origins of every project in your scope
  7. 15. extension that automatically creates comments on pull requests, which block check-in by policy, based on what files the pull request touches
  8. 16. __ __ __ system tracks a variety of health criteria for commits in the monorepo, such as build status and automation pass rates
  9. 17. Technology that scales Git for the size of the Office codebase
  10. 21. creator of Git
  11. 22. Git does not use Auto-___ in the Office Monorepo for line ending linting
  12. 23. Process of moving or combining a sequence of commits to a new base commit
  13. 26. Azure DevOps concept that automatically builds and tests code projects to make them available to others
  14. 27. number of approvals needed to complete a pull request, per compliance policy
  15. 28. ___ of a pull request (such as what build must succeed) are mostly determined by the branch you’re merging into
Down
  1. 1. General guidance is to perform a ___ merge when merging from a feature branch into a parent branch
  2. 2. default diff tool
  3. 3. ___ pull requests allow you to manually choose what pieces of the validation process to kick off
  4. 4. a tool for favoriting branches (required to successfully checkout remote branches)
  5. 6. Tool that limits your build to the appropriate list of projects
  6. 7. a common mistake is choosing the wrong ___ branch for where you’re merging your changes into
  7. 8. open source, distributed version control system
  8. 11. all team branches are seen in the ___ folder
  9. 13. MANAGER person elected to keep code flowing smoothly in a branch
  10. 14. ___ triggers a customizable Pull Request to automatically merge any official branch code back into main
  11. 18. a reporting, requirements management, project management, and orchestration engine system
  12. 19. source control management for Office predecessor of Git
  13. 20. __ __ automatically kick off cloud build buddy builds and code reviews
  14. 24. link to the CloudBuild outputs
  15. 25. root development branch for the Office monorepo