{"id":17284656,"url":"https://github.com/exu/skills-release-based-workflow","last_synced_at":"2025-03-26T16:25:59.014Z","repository":{"id":248114362,"uuid":"827799572","full_name":"exu/skills-release-based-workflow","owner":"exu","description":"My clone repository","archived":false,"fork":false,"pushed_at":"2024-07-12T11:59:12.000Z","size":79,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-01-31T21:07:00.665Z","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/exu.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":"2024-07-12T11:58:45.000Z","updated_at":"2024-07-12T11:59:15.000Z","dependencies_parsed_at":"2024-07-12T13:48:32.707Z","dependency_job_id":"4bbbc3f3-253e-4d67-a141-22010ee22c80","html_url":"https://github.com/exu/skills-release-based-workflow","commit_stats":null,"previous_names":["exu/skills-release-based-workflow"],"tags_count":0,"template":false,"template_full_name":"skills/release-based-workflow","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/exu%2Fskills-release-based-workflow","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/exu%2Fskills-release-based-workflow/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/exu%2Fskills-release-based-workflow/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/exu%2Fskills-release-based-workflow/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/exu","download_url":"https://codeload.github.com/exu/skills-release-based-workflow/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":245691035,"owners_count":20656693,"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-10-15T09:54:38.987Z","updated_at":"2025-03-26T16:25:58.986Z","avatar_url":"https://github.com/exu.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 1 \u003e\u003e\u003e\n  Choose 3-5 steps for your course.\n  The first step is always the hardest, so pick something easy!\n  Link to docs.github.com for further explanations.\n  Encourage users to open new tabs for steps!\n--\u003e\n\n## Step 1: Create a beta release\n\n_Welcome to \"Release-based workflow\" :sparkle:_\n\n### The GitHub flow\n\nThe [GitHub flow](https://guides.github.com/introduction/flow/) is a lightweight, branch-based workflow for projects with regular deployments.\n\n![github-flow](https://user-images.githubusercontent.com/6351798/48032310-63842400-e114-11e8-8db0-06dc0504dcb5.png)\n\nSome projects may deploy more often, with continuous deployment. There might be a \"release\" every time there's a new commit on main.\n\nBut, some projects rely on a different structure for versions and releases.\n\n### Versions\n\nVersions are different iterations of updated software like operating systems, apps, or dependencies. Common examples are \"Windows 8.1\" to \"Windows 10\", or \"macOS High Sierra\" to \"macOS Mojave\".\n\nDevelopers update code and then run tests on the project for bugs. During that time, the developers might set up certain securities to protect from new code or bugs. Then, the tested code is ready for production. Teams version the code and release it for installation by end users.\n\n### :keyboard: Activity: Create a release for the current codebase\n\nIn this step, you will create a release for this repository on GitHub.\n\nGitHub Releases point to a specific commit. Releases can include release notes in Markdown files, and attached binaries.\n\nBefore using a release based workflow for a larger release, let's create a tag and a release.\n\n1. Open a new browser tab, and work on the steps in your second tab while you read the instructions in this tab.\n1. Go to the **Releases** page for this repository.\n   - _Tip: To reach this page, click the **Code** tab at the top of your repository. Then, find the navigation bar below the repository description, and click the **Releases** heading link._\n1. Click **Create a new release**.\n1. In the field for _Tag version_, specify a number. In this case, use **v0.9**. Keep the _Target_ as **main**.\n1. Give the release a title, like \"First beta release\". If you'd like, you could also give the release a short description.\n1. Select the checkbox next to **Set as a pre-release**, since it is representing a beta version.\n1. Click **Publish release**.\n\n### :keyboard: Activity: Introduce a bug to be fixed later\n\nTo set the stage for later, let's also add a bug that we'll fix as part of the release workflow in later steps. We've already created a `update-text-colors` branch for you so let's create and merge a pull request with this branch.\n\n1. Open a **new pull request** with `base: release-v1.0` and `compare: update-text-colors`.\n1. Set the pull request title to \"Updated game text style\". You can include a detailed pull request body, an example is below:\n   ```\n   ## Description:\n   - Updated game text color to green\n   ```\n1. Click **Create pull request**.\n1. We'll merge this pull request now. 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/orgs/skills/discussions/categories/release-based-workflow) \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%2Fexu%2Fskills-release-based-workflow","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fexu%2Fskills-release-based-workflow","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fexu%2Fskills-release-based-workflow/lists"}