{"action":"closed","issue":{"url":"https://api.github.com/repos/hectorsector/release-based-workflow/issues/6","repository_url":"https://api.github.com/repos/hectorsector/release-based-workflow","labels_url":"https://api.github.com/repos/hectorsector/release-based-workflow/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/hectorsector/release-based-workflow/issues/6/comments","events_url":"https://api.github.com/repos/hectorsector/release-based-workflow/issues/6/events","html_url":"https://github.com/hectorsector/release-based-workflow/issues/6","id":381761897,"node_id":"MDU6SXNzdWUzODE3NjE4OTc=","number":6,"title":"Adding a feature","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":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-16T21:12:19Z","updated_at":"2018-11-16T21:12:54Z","closed_at":"2018-11-16T21:12:54Z","author_association":"NONE","body":"## Release management\n\nAs you prepare for a future release, you'll need to organize more than the tasks and features. It's important to create a clear workflow for your team, and to make sure that the work remains organized.\n\nThere are several strategies for managing releases. Some teams might use long-lived branches, like `production`, `dev`, and `master`. Some teams use simple feature branches, releasing from the master branch.\n\nNo one strategy is better than another. We always recommend being intentional about branches and reducing long-lived branches whenever possible.\n\nIn this exercise, you'll use the `release-v1.0` branch to be your one long-lived branch per release version.\n\n## Protected branches\n\nLike the `master` branch, you can protect release branches. This means you can protect branches from force pushes or accidental deletion. This is already configured in this repository.\n\n## Add a feature\n\nReleases are usually made of many smaller changes.  This is a practice repository, but we will still make at least two feature adjustments.\n\nSince we don't know of any bugs, we'll focus on a few features to update on our game before the version update.\n\n- [ ] Update the README.md to point to the correct game URL\n- [ ] Change the text colors to green\n\n## Step 5: Adding a feature\n\nFirst, update the URL in your README.md.\n\nUsing the GitHub flow, make your update, and open a pull request with `release-v1.0` as your base branch.\n\n### :keyboard: Activity: Update the README.md\n\n1. Create a new branch and change the URL in the `README.md` to point to your own GitHub Pages site, `https://hectorsector.github.io/release-based-workflow`\n1. Open a pull request with `release-v1.0` as the `base` branch, and your new branch as `compare`.\n1. Fill in the pull request template to describe your changes.\n\n<hr>\n<h3 align=\"center\">I'll respond in your pull request with the next step.</h3>\n"}}
{"actor":{"display_login":"hectorsector-bananas"}}