Squash with Default Message Integration Strategy

jtherzoff commented 1 year ago

name: '#4 Task' about: 'Task that should be linked to user story #1' title: 'Squash with Default Message Integration Strategy' labels: '' assignees: ''

References user story #1

TODO:

[ ] :question: Answer question Task4_Q1 on Canvas
[ ] :bust_in_silhouette: Assign yourself to this task (this will prompt the WorkflowLearning GitHub App to create the task_4_squash branch)
[ ] :hourglass_flowing_sand: Wait (at most) 60 seconds until the WorkflowLearning GitHub App will comment on this task and confirm that the branch task_4_squash was created (refresh the page if you don't see the confirmation comment)
[ ] Create a new PR having the base branch master and the compare branch task_4_squash
[ ] Edit the description of the PR to reference this task
[ ] :brain: Understand the commits and file changes made in the PR
[ ] :question: Answer question Task4_Q2 on Canvas
[ ] :arrows_counterclockwise: Refresh this page (to ensure that any commits referencing this task are shown on this page) and scroll all the way to the bottom of the page
[ ] :question: Answer question Task4_Q3 on Canvas

Starting integration...

[ ] In the PR, integrate the changes into master
using the Squash and merge option
with the squashed commit message Task 4 squash (#<ID_PR>) (i.e., the default commit message provided by GitHub) NOTE: do NOT make any changes to the squashed commit extended description (which lists the individual commits that are in the pull request)

Integration completed.

[ ] :eyes: Inspect the history of all the branches and commits via Insights -> Network
NOTE: all the commits from branch task_4_squash were squashed/compressed/bundled into a single "atomic" commit that was added to the master branch
[ ] :x: In the PR, use the GitHub interface to delete the branch (since the branch content was successfully integrated into master)
[ ] :eyes: Inspect the history of all the branches and commits via Insights -> Network
NOTE: the branch task_4_squash was deleted successfully from the repository, reducing the repository clutter
[ ] :arrows_counterclockwise: Refresh this page (to ensure that any commits referencing this task are shown on this page) and scroll all the way to the bottom of the page
[ ] :question: Answer question Task4_Q4 on Canvas
[ ] :question: Answer question Task4_Q5 on Canvas

workflowlearning[bot] commented 1 year ago

:runner: Creating branch `task_4_squash`...

:hourglass_flowing_sand: Please wait (at most) 60 seconds until the WorkflowLearning GitHub App will add a new comment to this task and confirm that the branch task_4_squash was created successfully (refresh the page if you don't see the confirmation comment).

Additional details

Detected event = `assigned` Branch to be created (containing a few commits) = `task_4_squash` Repository full name = `jtherzoff/jtherzoff-CS471WorkflowsHomeworkAssignment` Issue number = `#4` Issue title = 'Squash with Default Message Integration Strategy' Assignee login = 'jtherzoff' ---

FAQ

**Q: What type of events trigger the [WorkflowLearning GitHub App](https://github.com/apps/workflowlearning) to create a new branch containing a series of commits?** - a developer is assigned to issues `#2`, `#3`, `#4`, `#5` and `#6` in a repository called `CS471WorkflowsHomeworkAssignment`

Beta Disclaimer

[WorkflowLearning GitHub App](https://github.com/apps/workflowlearning) `v1.0.0` (see [Semantic Versioning](https://semver.org/)) is an experimental [GitHub Application](https://developer.github.com/apps/) that attempts to provide a "sandbox" environment for learning about different **workflow integrations**, such as merge, rebase and squash. This bot is still in **BETA**, and if you think the feedback provided is inaccurate please submit a bug report (i.e., email the instructor) and you can get extra credit.

#### Debug Information ``` github_event = issues payload_action = assigned request_number = 374 ```

workflowlearning[bot] commented 1 year ago

:thumbsup: Branch `task_4_squash` was created successfully

Please continue with the next steps as specified in the task description.

Additional details

---

FAQ

**Q: What type of events trigger the [WorkflowLearning GitHub App](https://github.com/apps/workflowlearning) to create a new branch containing a series of commits?** - a developer is assigned to issues `#2`, `#3`, `#4`, `#5` and `#6` in a repository called `CS471WorkflowsHomeworkAssignment`

Beta Disclaimer

[WorkflowLearning GitHub App](https://github.com/apps/workflowlearning) `v1.0.0` (see [Semantic Versioning](https://semver.org/)) is an experimental [GitHub Application](https://developer.github.com/apps/) that attempts to provide a "sandbox" environment for learning about different **workflow integrations**, such as merge, rebase and squash. This bot is still in **BETA**, and if you think the feedback provided is inaccurate please submit a bug report (i.e., email the instructor) and you can get extra credit.

#### Debug Information ``` github_event = issues payload_action = assigned request_number = 374 ```

jtherzoff / jtherzoff-CS471WorkflowsHomeworkAssignment