{"action":"opened","issue":{"url":"https://api.github.com/repos/hectorsector/release-based-workflow/issues/3","repository_url":"https://api.github.com/repos/hectorsector/release-based-workflow","labels_url":"https://api.github.com/repos/hectorsector/release-based-workflow/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/hectorsector/release-based-workflow/issues/3/comments","events_url":"https://api.github.com/repos/hectorsector/release-based-workflow/issues/3/events","html_url":"https://github.com/hectorsector/release-based-workflow/issues/3","id":378048210,"node_id":"MDU6SXNzdWUzNzgwNDgyMTA=","number":3,"title":"Creating a release branch","user":{"login":"hectorsector-bananas[bot]","id":29761101,"node_id":"MDM6Qm90Mjk3NjExMDE=","avatar_url":"https://avatars1.githubusercontent.com/u/16547949?v=4","gravatar_id":"","url":"https://api.github.com/users/hectorsector-bananas%5Bbot%5D","html_url":"https://github.com/apps/hectorsector-bananas","followers_url":"https://api.github.com/users/hectorsector-bananas%5Bbot%5D/followers","following_url":"https://api.github.com/users/hectorsector-bananas%5Bbot%5D/following{/other_user}","gists_url":"https://api.github.com/users/hectorsector-bananas%5Bbot%5D/gists{/gist_id}","starred_url":"https://api.github.com/users/hectorsector-bananas%5Bbot%5D/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hectorsector-bananas%5Bbot%5D/subscriptions","organizations_url":"https://api.github.com/users/hectorsector-bananas%5Bbot%5D/orgs","repos_url":"https://api.github.com/users/hectorsector-bananas%5Bbot%5D/repos","events_url":"https://api.github.com/users/hectorsector-bananas%5Bbot%5D/events{/privacy}","received_events_url":"https://api.github.com/users/hectorsector-bananas%5Bbot%5D/received_events","type":"Bot","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-06T21:50:09Z","updated_at":"2018-11-06T21:50:09Z","closed_at":null,"author_association":"NONE","body":"## Release management\n\nAs you prepare for a future release, you'll need to organize more than just the tasks and features. It's equally important to create a clear branching workflow for your team, and to make sure that the work remains organized logically.\n\nThere are several strategies for managing releases. Some teams might use dozens of long-lived branches, like `production`, `dev`, `master`, `release-version`. Some teams don't use branching at all, cutting releases directly from the master branch and leaving tags behind in case they need to bugfix later.\n\nFor this workflow, we recommend that you create one long-lived branch per release version.\n\n## Protected branches\n\nWhen you create a release branch, it should generally be treated with the same care as a `master` branch. This means that, at minimum, it should be protected from force pushing or accidental deletion. We'll do this for you automatically for this course, but recommend that you [configure protected branches](https://help.github.com/articles/configuring-protected-branches/) if you use this strategy on future projects.\n\n## Step 5: Creating a branch\n\nAs you learned in the GitHub flow, create a new, long-lived branch from the **Code** tab using a deliberate naming convention.\n\nCompletion of this task resolves #2. Once I close this issue for you, our automated project board should move our \"Organizing a release\" task to completion.\n\n<details><summary>Why?</summary>\n\nAll issues and pull requests can be closed [via keywords](https://help.github.com/articles/closing-issues-using-keywords/).\n\nSince this issue relates to organizing a release, I linked it to our previous issue with a direct mention (`#2`). Once this task is complete, I'll close the issue. When this issue closes, it will also close #2, due to the use of `close` and `resolves` as keywords. Assuming we set up automation on our project board correctly, an issue closure will move an \"In Progress\" issue that is closed to the \"Done\" column.\n\n</details>\n\n\n### :keyboard: Activity: Create a branch\n\n1. Create a new branch, and make sure it's titled `release-v1.0` (warning: If naming doesn't match exactly, you'll run into unexpected errors later in the course)\n\n<hr>\n<h3 align=\"center\">I'll respond below for your next step</h3>\n"}}
{"actor":{"display_login":"hectorsector-bananas"}}