{"id":21400355,"url":"https://github.com/tcarters/skills-release-based-workflow","last_synced_at":"2025-03-16T15:55:25.318Z","repository":{"id":175958655,"uuid":"654769596","full_name":"Tcarters/skills-release-based-workflow","owner":"Tcarters","description":"My clone repository","archived":false,"fork":false,"pushed_at":"2023-10-01T21:22:08.000Z","size":89,"stargazers_count":0,"open_issues_count":1,"forks_count":0,"subscribers_count":2,"default_branch":"main","last_synced_at":"2025-01-23T02:44:44.925Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Tcarters.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-06-16T23:08:27.000Z","updated_at":"2023-06-16T23:08:33.000Z","dependencies_parsed_at":null,"dependency_job_id":"68cf8a0c-b474-4312-b07a-7c2cb6ee5d7d","html_url":"https://github.com/Tcarters/skills-release-based-workflow","commit_stats":null,"previous_names":["tcarters/skills-release-based-workflow"],"tags_count":1,"template":false,"template_full_name":"skills/release-based-workflow","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Tcarters%2Fskills-release-based-workflow","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Tcarters%2Fskills-release-based-workflow/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Tcarters%2Fskills-release-based-workflow/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Tcarters%2Fskills-release-based-workflow/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Tcarters","download_url":"https://codeload.github.com/Tcarters/skills-release-based-workflow/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":243893905,"owners_count":20364916,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-22T15:21:27.926Z","updated_at":"2025-03-16T15:55:25.243Z","avatar_url":"https://github.com/Tcarters.png","language":"JavaScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003cheader\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Course header \u003e\u003e\u003e\n  Read \u003chttps://skills.github.com/quickstart\u003e for more information about how to build courses using this template.\n  Include a 1280×640 image, course name in sentence case, and a concise description in emphasis.\n  In your repository settings: enable template repository, add your 1280×640 social image, auto delete head branches.\n  Next to \"About\", add description \u0026 tags; disable releases, packages, \u0026 environments.\n  Add your open source license, GitHub uses the MIT license.\n--\u003e\n\n# Create a release based workflow\n\n_Create a release based workflow that is built on the foundations of the GitHub flow._\n\n\u003c/header\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Step 2 \u003e\u003e\u003e\n  Start this step by acknowledging the previous step.\n  Define terms and link to docs.github.com.\n--\u003e\n\n## Step 2: Add a new feature to the release branch\n\n_Great job creating a beta release :heart:_\n\n### 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 `main`. Some teams use simple feature branches, releasing from the main 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 `main` 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. Let's pretend we don't know about the bug we added earlier and we'll focus on a few features to update our game before the version update.\n\n- You should update the page background color to black.\n- I'll help you change the text colors to green.\n\n### :keyboard: Activity: Update `base.css`\n\n1. Create a new branch off of the `main` branch and change the `body` CSS declaration in `base.css` to match what is below. This will set the page background to black.\n\n```\nbody {\n    background-color: black;\n}\n```\n\n1. Open a pull request with `release-v1.0` as the `base` branch, and your new branch as the `compare` branch.\n1. Fill in the pull request template to describe your changes.\n1. Click **Create pull request**.\n\n### Merge the new feature to the release branch\n\nEven with releases, the GitHub flow is still an important strategy for working with your team. It's a good idea to use short-lived branches for quick feature additions and bug fixes.\n\nMerge this feature pull request so that you can open the release pull request as early as possible.\n\n### :keyboard: Activity: Merge the pull request\n\n1. Click **Merge pull request**, and delete your branch.\n1. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.\n\n\u003cfooter\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Footer \u003e\u003e\u003e\n  Add a link to get support, GitHub status page, code of conduct, license link.\n--\u003e\n\n---\n\nGet help: [Post in our discussion board](https://github.com/skills/.github/discussions) \u0026bull; [Review the GitHub status page](https://www.githubstatus.com/)\n\n\u0026copy; 2023 GitHub \u0026bull; [Code of Conduct](https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md) \u0026bull; [MIT License](https://gh.io/mit)\n\n\u003c/footer\u003e\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftcarters%2Fskills-release-based-workflow","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ftcarters%2Fskills-release-based-workflow","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftcarters%2Fskills-release-based-workflow/lists"}