From ffdb2e2fac65ea114731c9ad6496625b81e3cf99 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Mon, 15 Dec 2025 13:58:37 -0800 Subject: [PATCH 01/52] Revise GitHub organizations documentation for clarity Updated the document to clarify the roles of GitHub organizations for B.C. Government, including changes to Single Sign-On (SSO) details and security features. --- .../bc-government-organizations-in-github.md | 160 +++++++++--------- 1 file changed, 84 insertions(+), 76 deletions(-) diff --git a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md index 7039bec..7f18640 100644 --- a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md +++ b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md @@ -1,124 +1,132 @@ # B.C. Government organizations in GitHub -The [Digital Principles for B.C. Government](https://www2.gov.bc.ca/gov/content/governments/policies-for-government/core-policy/policies/im-it-management#12.1.1.5) urge product teams to work in the open. GitHub is the leading platform for open-source projects. It lets our organization work with the open-source community to build software, support innovation and save time and money. +The [Digital Principles for B.C. Government](https://www2.gov.bc.ca/gov/content/governments/policies-for-government/core-policy/policies/im-it-management#12.1.1.5) supports and encourages product teams to work in the open. GitHub **(GH)** is the leading platform for open-source projects and collaboration. -Using GitHub, teams can: +With GiHub Enterprise Cloud, we can: + - Collaborate with the open-source community to build software + - Support innvation + - Share code and best practices + - Track issues and feature requests + - Use tools for team and project management + - Save costs and time -* Collaborate with the open-source community -* Share and control code versions -* Use tools for team and project management -* Integrate automation tools -* Track issues +The **Developer Experience team** manages B.C. Government's GitHub environments. For questions, concerns, or feedback, please [submit a support request on JSM]( https://citz-do.atlassian.net/servicedesk/customer/portal/2). -!!! Info - This document aims to provide detailed information about accessing B.C. government's GitHub organizations. If you are looking for quick access to common topics related to using GitHub in the B.C. government, you may wish to consult our [quick reference](quick-reference.md) instead. +For users who need quick access to common topics related to using GitHub in B.C. Government, please see the [GitHub for B.C. Government quick reference guide](docs/sample-govorginGH-quickref.md) instead of this doc. -B.C. Government's main organization is [bcgov](https://github.com/bcgov), where we store open code developed by government teams. It includes projects that have open-source and inner-source contribution models. `bcgov` has over 1000 repositories. +## Organizations in GitHub -We also have the `bcgov-c` organization, where developers can store confidential code. +We have two GitHub organizations **(org)**: `bcgov` and `bcgov-c`: -On behalf of the B.C. Government, the Developer Experience Team manages government GitHub environments. For any questions or concerns, please [submit a support request]( https://citz-do.atlassian.net/servicedesk/customer/portal/2). +```mermaid +graph TD; + A[GitHub Enterprise Cloud] --> B[bcgov]; + A --> C[bcgov-c]; +``` +On July 2024, we enabled Single-Sign on **(SSO)** for `bcgov`. For `bcgov-c`, we enabled SSO on August 2024. All members must be authenticated with IDIRs, including contractors. Our [Single Sign-On (SSO) doc](#single-sign-on) has more information about the transition. -## Organizations in GitHub +To link GH accounts and IDIRs, [follow the SSO enablement instructions](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/bc-government-organizations-in-github/#directions-to-sign-up-and-link-your-account-for-bcgov). -!!! Note +### `bcgov` - In July 2024, we enabled [Single Sign-On (SSO)](#single-sign-on) for `bcgov` and in August 2024, `bcgov-c`. To keep access to repositories in the `bcgov` and `bcgov-c` organizations, all users must be authenticated with IDIRs. Contractors and employees without IDIRs must order one before SSO can be enabled. +The `bcgov` org hosts public repositories **(repos)** and has over 1000 repos. Each repo holds open-source code, public documents, and inner-source contribution models developed by B.C. government teams. -We use GitHub Enterprise Cloud, and it hosts the `bcgov` and `bcgov-c` GitHub organizations: +All content in this org must be public to align with [B.C. Government's Digital Principles](https://digital.gov.bc.ca/policies-standards/dcop/). Anyone with membership can create repos. -```mermaid - graph TD; -A[GitHub Enterprise Cloud] --> B[bcgov] -A --> C[bcgov-c] -``` +### `bcgov-c` -### `bcgov` +We use `bcgov-c` for **private** repos with confidential code and documents. If a team needs a location for private code, or is working to make code public, this is the right org. -The `bcgov` organization contains public repositories that hold open-source code or public documents developed by B.C. government teams. This organization is **public**. To align with our Digital Principles, repositories should be hosted in this open repo. The only exception is strong rationale from your Ministry Security Information Officer. +Only the Developer Experience team can create repos in `bcgov-c`. To request a repo, please [submit a support request on JSM](https://citz-do.atlassian.net/servicedesk/customer/portal/2/group/9/create/60). -* Any member of the `bcgov` organization can create repositories. +### Security features for both organizations -* To join this organization, follow [these instructions](#directions-to-sign-up-and-link-your-account-for-bcgov). +Please keep in mind that application and code security are complex. The [Security and Privacy Guidance](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/security/security-and-privacy-compliance-and-guidance/) and [Security best practices for apps](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/security/best-practices-for-apps/) docs offers more comprehensive guidance. -### `bcgov-c` +Both orgs come with various security features to protect repos and its code. We've highlighted some prominent features and best practices below. -The `bcgov-c` organization stores private repositories with confidential source code and documents. This repository is **private**. +#### Costs -* Use this repository if you need a location for private code, or if you're working towards making the code public. -* Only the Developer Experience team can create repositories in this organization. - * Request a repository by [submitting a request](https://citz-do.atlassian.net/servicedesk/customer/portal/2/group/9/create/60). -* To join this organization, follow [these instructions](#directions-to-sign-up-and-link-your-account-for-bcgov-c). +**`bcgov`:** no cost for security features because GH gives them free to public repos. +**`bcgov-c`**: cost for security features because GH charges a fee for private repos. **But** the Developer Experience team covers cost **without cost recovery**. -## Single Sign-On +#### Prominent features -!!! Warning - Contractors without an IDIR must follow the steps in [our guide](github-transition-guide.md#idirs) before proceeding. **Please note** this can take several days to complete depending on your ministry. We recommend doing with this step as soon as possible to avoid access disruptions. +* **Code scanning:** scans code for security vulnerabilities and coding errors. -Learn more about IDIRs and post-authentication steps in [our guide](github-transition-guide.md). - -### Directions to sign up and link your account for 'bcgov' +* **Secret scanning:** scans repos and commits for sensitive information like API keys, passwords, and other secrets. -1. Have any two-factor devices, and personal GitHub login and IDIR login ready. -1. Log into GitHub with your personal login. -1. [Authenticate your IDIR](https://github.com/orgs/bcgov/sso) -1. You'll get an email with an invitation to join the **bcgov** GitHub organization. The invitation will be sent to the email address associated with your GitHub account. - 1. Refer to the [troubleshooting](#troubleshooting) section if you didn't receive an email. -1. Your teammates can add you to your team's repositories. We recommend teams use [GitHub teams](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. -1. [Authorize your personal access tokens and/or SSH keys](github-transition-guide.md#resetting-github-keys). +* **Dependabot:** scans repos for outdated or vulnerable dependencies and provides recommendations for fixing problems, including via automated pull requests **(PR)**. -That’s it, your accounts are now joined. +#### Best practices -[Learn more about IDIRs](github-transition-guide.md). - -### Directions to sign up and link your account for 'bcgov-c' +* **Keep features enabled in repos**. Even if some can be reconfigured at the repo level, they're there the team secure code. -A similar process applies for 'bcgov-c'. +* **Use the GH [Security Overview page](https://github.com/orgs/bcgov/security/overview)** to check any detected issues for repos, especially if working on multiple repos. -1. Have any two-factor devices, and personal GitHub login and IDIR login ready. -1. Log into GitHub with your personal login. -1. [Authenticate your IDIR](https://github.com/orgs/bcgov-c/sso) -1. You'll get an email with an invitation to join the **bcgov-c** GitHub organization. The invitation will be sent to the email address associated with your GitHub account. - 1. Refer to the [troubleshooting](#troubleshooting) section if you didn't receive an email. -1. Your teammates can add you to your team's repositories. We recommend teams use [GitHub teams](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. -1. [Re-authorize your personal access tokens and/or SSH keys](github-transition-guide.md#resetting-github-keys). +* **Take action on any issue surfaced by security features immediately**. Quick action-even if false positives-can stop big problems or becoming "noise" to ignore. -That’s it, your accounts are now joined. -[Learn more about IDIRs](github-transition-guide.md) +## Single Sign-On -#### Video demo'ing joining GitHub ID and IDIR +Because IDIRs are mandatory for both organizations, we have created an [IDIR guide](github-transition-guide.md). We've also included contractor-specific instructions. Please note that IDIR order completion can take **several** days. -The video shows the process, starting from the banner link on the `bcgov` GitHub organization, to the end: +If the instructions and troubleshooting help below doesn't resolve any issues, please [submit a support request on JSM]( https://citz-do.atlassian.net/servicedesk/customer/portal/2). - +### Security Insights for GitHub Enterprise-linked organizations -### SSO timelines for 'bcgov-ent' +All orgs linked to the corporate GitHub Enterprise accounts have access to the Security Insight feature, inclusive of branch protection and code owners for private repos. -For current B.C. Government private organizations part of the legacy `bcgov-ent` Enterprise implementation, we’ll work with your respective Information Management Branches and Information Systems Branches to identify next steps. - -### Resources - -For more supplementary information, please see [our guide](github-transition-guide.md). +Branch protection allows specified members to push to the protected branch. The code owners feature allows automated reviews. For example, if a member is a code owner of certain files, they'll automatically be added as a PR reviewer. A PR needs their approval before the code can be merged. + +### Directions to sign up and link your account for `bcgov` + +1. Have any two-factor device, and personal GitHub login and IDIR login ready. +2. Log into GitHub with your personal login. +3. [Authenticate your IDIR](https://github.com/orgs/bcgov/sso) +4. You'll get an email with an invitation to join the `bcgov` GitHub organization. The invitation will be sent to the email address associated with your GitHub account. + a. Refer to the [troubleshooting](#troubleshooting) section if you didn't receive an email. +5. Your teammates can add you to your team's repositories. We recommend teams use [GitHub teams](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. +6. [Authorize your personal access tokens and/or SSH keys](github-transition-guide.md#resetting-github-keys). + +That’s it, both accounts are now joined. -For help with access, please [submit a support request]( https://citz-do.atlassian.net/servicedesk/customer/portal/2). +### Directions to sign up and link your account for `bcgov-c` + +A similar process applies for `bcgov-c`. + +1. Have any two-factor devices, and personal GitHub login and IDIR login ready. +1. Log into GitHub with your personal login. +1. [Authenticate your IDIR](https://github.com/orgs/bcgov-c/sso) +1. You'll get an email with an invitation to join the `bcgov-c` GitHub organization. The invitation will be sent to the email address associated with your GitHub account. + 1. Refer to the [troubleshooting](#troubleshooting) section if you didn't receive an email. +1. Your teammates can add you to your team's repositories. We recommend teams use [GitHub teams](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. +1. [Re-authorize your personal access tokens and/or SSH keys](github-transition-guide.md#resetting-github-keys). -## Security Insights for GitHub Enterprise-linked organizations +That’s it, both accounts are now joined. -The Security Insight feature is available for all organizations linked to the corporate GitHub Enterprise accounts, as well as branch protection and code owners for private repositories. Branch protection only allows specific people to push to the protected branch. The code owners feature allows automated reviews. For example, if a specific user is a code owner of certain files they are automatically added as PR reviewers and their approval is required before the code can be merged. +### SSO video demo -## Troubleshooting + -### I didn't receive an email invitation to join the bcgov or bcgov-c organization +### Troubleshooting -You can check your organization status and invites: +If you didn't get an email invitation to join either organizations, you can check your organization status and invites: 1. Go to [https://github.com](https://github.com) -1. Sign in with the account used to join the [bcgov](#directions-to-sign-up-and-link-your-account-for-bcgov) or [bcgov-c](#directions-to-sign-up-and-link-your-account-for-bcgov-c) organization +1. Sign in with the account used to join the [`bcgov`](#directions-to-sign-up-and-link-your-account-for-bcgov) or [`bcgov-c`](#directions-to-sign-up-and-link-your-account-for-bcgov-c) organization 1. Click on your profile picture 1. Choose the "Your organizations" option from the menu -1. Confirm the bcgov and/or bcgov-c organization is listed under the "Organizations" page +1. Confirm the `bcgov` and/or `bcgov-c` organization is listed under the "Organizations" page 1. Click the "Accept" button next to the organization -![Screenshot of a user's organizations. The screen displays the bcgov-c organization with "Member" beside it. Next to it is "Invitation expires in 7 days" with Accept and Decline buttons.](../images/invitation.png) +![Screenshot of a user's organizations. The screen displays the `bcgov-c` organization with "Member" beside it. Next to it is "Invitation expires in 7 days" with Accept and Decline buttons.](../images/invitation.png) From c32fb04a4975e68182f24f7a08bdbfc69ec92b76 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Mon, 15 Dec 2025 14:58:10 -0800 Subject: [PATCH 02/52] Revise license guidelines for GitHub repositories Updated the license guidelines and structure for GitHub repositories, including new sections on authority and applying licenses. Enhanced clarity on the types of licenses and their usage. --- .../license-your-github-repository.md | 172 +++++++++++------- 1 file changed, 103 insertions(+), 69 deletions(-) diff --git a/docs/use-github-in-bcgov/license-your-github-repository.md b/docs/use-github-in-bcgov/license-your-github-repository.md index 6d4e15b..8e3fb3c 100644 --- a/docs/use-github-in-bcgov/license-your-github-repository.md +++ b/docs/use-github-in-bcgov/license-your-github-repository.md @@ -1,83 +1,126 @@ ---- -title: License your GitHub repository +# Licenses for GitHub repos -slug: license-your-github-repository +Licences manage and share intellectual property for code and materials on GitHub. Any consumpation, shares, or contributions to a repo needs to be matched with the relevant licence. -description: Describes licence guidelines and the different types of licences used for GitHub repositories -keywords: licence, license, apache 2.0, BC OGL, Creative Commons, Affero, repository management, repository best practices +The Intellectual Property Program **(IPP)** must approve licences of B.C. government owned intellectual property. The only **exception** is if a ministry has either specific legislative authority or Treasury Board approval that lets them license the intellectual property rights of the Province to third parties. -page_purpose: Outlines how to choose and use a licence for your project and describes the requirements around licensing +When IPP is the authority for the licensing, teams must work with IPP to find the best fit to meet the licensing needs of the project. -audience: developer, technical lead - -author: Jonathan Bond - -content_owner: Olena Mitovska, Nick Corcoran - -sort_order: 9 ---- -# License your GitHub repository - -Licences help you manage and share intellectual property for code and materials on GitHub. If you want to consume, share or contribute to anything in GitHub, you have to understand requirements associated with the relevant licence. - -## On this page - -- [Licence guidelines](#licence-guidelines) -- [Authority to license](#authority-to-license) -- [Choose a licence](#choose-a-licence) -- [Apply the licence to your project](#apply-the-licence-to-your-project) - -## Licence guidelines - -Note if the licence attached to material restricts modification or redistribution of the content. If a licence isn't attached to content, assume that it's "all rights reserved" and can't be used without the express permission of the copyright owner. - -### Contribute to a project - -If you want to contribute to an existing, outside project, make sure you understand the applicable licence and contributor requirements. If the project needs copyright assignment or a contributor agreement, contact the Legal Services Branch before taking any action. - -### Initiate a project - -If want to initiate a project or release previously created materials, be aware that the Province can only license rights that it is in a legal position to grant to others. - -The Province’s intellectual property rights must be, at a minimum, equal to the rights under which the content will be licensed to third parties. Four open licences are approved for use that likely cover the majority of projects coming forward: - -## Authority to license - -The Intellectual Property Program (IPP) must approve licences of B.C. government owned intellectual property unless a ministry has either specific legislative authority or Treasury Board approval that lets them license the intellectual property rights of the Province to third parties. When IPP is the authority for the licensing, you work with IPP to find the best fit to meet the licensing needs of the project. - -IPP examines the development history of the content, which can take the form of a conversation. Initial questions include the following: +IPP examines the development history of the content, somtetimes in the form of a conversation. Initial questions include the following: - Is the content created solely by B.C. government employees? + - Does the content contain only content owned by the B.C. government? Have you made sure that it doesn't contain any third-party content? - Can you confirm that there are no terms of use or exclusive licensing arrangements that prohibit the Province from posting and licensing the content on GitHub? -### Preferred licenses +## Guidance for choosing a licence -- [Apache 2](https://www.apache.org/licenses/LICENSE-2.0) for publishing code. -- [Creative Commons International 4.0 (CC BY)](https://creativecommons.org/licenses/by/4.0/) for other documentation, artistic resources and educational material. -- [Open Government Licence - BC (OGL-BC)](https://www2.gov.bc.ca/gov/content/data/open-data/open-government-licence-bc) for making government generated and owned data available to the public. -- [Affero General Public Licence (AGPL)](https://www.gnu.org/licenses/agpl-3.0.en.html) for works already containing that licence or for which maintaining open access to any modifications is critical. +Always determine if a licence attached to material restricts changes or resharing of content. If it doesn't, then the assumption of "all rights reserved" applies. It cannot be used with the explicit permission of the rights holder. -Use these licences, as they are widely accepted, and follow a consistent approach to licensing. This increases efficiency for both developers and consumers. +Below, we've outlined some guidelines to help teams get started. -If your project is better suited to a different licence, discuss your requirements with the IPP. They can help answer your questions and advise on your need for any other legal or risk management advice. +### Contributing to a project -## Choose a licence +Even when contributing to an existing, external project, teams must understand the licence and contributor conditions. If any project needs a copyright assignment or contributor agreement, please contact the Legal Services Branch **(LSB)** before taking any action. -The following overview provided is intended to inform, not replace, the licensing review for each project. If you think you need to engage with the Intellectual Property Program, send a request to the IPP Manager +### Initiating a project -![A flowchart that helps you choose a licence](images/licence-chart.png) +B.C. Goverment can only license rights that it's in a legal position to grant others. If a team wants to initiate a project or release materials created prior, please make sure that government's intellectual property right are, minimally, equal to the rights under which the content will be licensed to third parties. -If your project is related to a community that typically uses a different licence than one of the preferred licences described above, or if you have any questions about which licence best applies to your project, contact IPP. +As of **2026**, four open licences have been approved to use that most likely covers many projects: -![A flowchart to outline code preparation for GitHub](images/github-code-preparation-chart.png) +- [Apache 2](https://www.apache.org/licenses/LICENSE-2.0) for publishing code. -## Apply the licence to your project +- [Creative Commons International 4.0 (CC BY)](https://creativecommons.org/licenses/by/4.0/) for other documentation, artistic resources and educational material. -Place the licence file for your project in the repository before you do anything else. The default license for code repositories is Apache 2.0. +- [Open Government Licence - BC (OGL-BC)](https://www2.gov.bc.ca/gov/content/data/open-data/open-government-licence-bc) for making government generated and owned data available to the public. -Use the following boiler-plate text in the comments header of every source code file, as well as the bottom of your README.md: +- [Affero General Public Licence (AGPL)](https://www.gnu.org/licenses/agpl-3.0.en.html) for works already containing that licence or for which maintaining open access to any modifications is critical. + +These four follow a consistent licensing approach. But, if a project is better suited to a difference licence, talk about the requirements with the IPP. They can answer questions and advise on further actions. + +## Choosing a licence + +The following flowcharts represent the above in a detailed, visual way. We offer the diagrams in hopes to inform, not replace, the licensing review for each project. + +The first flowchart guides a team choosing one of the four approved licences for their project: + +```mermaid +%%{ + init: { + 'theme': 'base', + 'themeVariables': { + 'primaryColor': '#3333ff', + 'primaryTextColor': '#fff', + 'primaryBorderColor': '#7C0000', + 'lineColor': '#F8B229', + 'secondaryColor': '#3399ff', + 'tertiaryColor': '#6699ff' + } + } +}%% + +flowchart TD + accTitle: Choosing an approved license. + accDescr: Mermaid diagram flowchart showing pathways for teams to chose one of the four approved licenses. + + A[Start] -->B(Prohibit commericial use of distribution of adaptations?) + B --> |Yes| C(More investigation with RMB, IPP, and/or LSB needed) + B---> |No| D(License for software or code?) + D --> |Yes| E(Apache 2.0) + D --> |No| F(License for data-only generated and owned by BC Govt?) + F --> |Yes| G(BC - OGL) + F --> |No| H(Atrribution 4.0 International CC-BY) +``` + +The second flowchart shows a path of self-assessment using some of the questions from the [Licenses for GitHub repo section](#Licenses-for-GitHub-repos) of this doc: + +```mermaid + +%%{ + init: { + 'theme': 'base', + 'themeVariables': { + 'primaryColor': '#3333ff', + 'primaryTextColor': '#fff', + 'primaryBorderColor': '#7C0000', + 'lineColor': '#F8B229', + 'secondaryColor': '#3399ff', + 'tertiaryColor': '#6699ff' + } + } +}%% + +flowchart TD + accTitle: Self-assessment for meeting with IPP or follow open development standards + accDescr: Mermaid diagram flowchart showing pathways for teams that lead to IPP or continue with open development standards. + + A[Start] -->B(Does content already exist?) + B --> |Yes| C(Created by only BC Gov employees?) + C --> |Yes| H + C --> |No| D(Contact IPP for help) + D --> |After guidance| H + B --> |No| E(Contributing to a project started by an **external** org?) + E --> |No| H(Answered **yes** to all questions in **Content Approval Checklist**?) + H --> |Yes| I(Will a pre-approved Open License suit project?) + H --> |No| N + I --> |No| M + I --> |Yes| J(Confirmed authority to license?) + J --> |No| M(More investigation with RMB, IPP and/or LSB needed) + J --> |Yes| K(Confirmed team's using the right GH org?) + K --> |No| M + K --> |Yes| L(**Cleared**: follow the open development standards) + E --> |Yes| F(Project operating under approved OSI license?) + F --> |No| N(More investigation with RMB, IPP and/or LSB needed) + F --> |Yes| G(Project needs to assign copyright or sign contributor agreement?) +``` + +## Applying the licence to a project + +Place the licence file for the project in the repo before anything else is done. The default license for code repositories is **Apache 2.0**. + +Use the following boiler-plate text in the comments header of every source code file, as well as the bottom of the **README** file: Copyright 2019 Province of British Columbia @@ -93,7 +136,7 @@ Use the following boiler-plate text in the comments header of every source code See the License for the specific language governing permissions and limitations under the License. -For repositories that are made up of docs, wikis or other non-code files, the default licence is Creative Commons Attribution 4.0 International. It should look like this at the bottom of your README.md: +For repositories that are made up of docs, wikis or other non-code files, the default licence is Creative Commons Attribution 4.0 International. It should look like this at the bottom of the README file: Creative Commons Licence
YOUR REPO NAME HERE by the Province of British Columbia is licensed under a Creative Commons Attribution 4.0 International License. @@ -105,12 +148,3 @@ The code for the Creative Commons 4.0 footer looks like this: xmlns:cc="http://creativecommons.org/ns#" property="cc:attributionName">the Province of British Columbia is licensed under a Creative Commons Attribution 4.0 International License. ---- -Related links: - -- [Apache 2](https://www.apache.org/licenses/LICENSE-2.0) -- [Creative Commons International 4.0 (CC BY)](https://creativecommons.org/licenses/by/4.0/) -- [Open Government Licence - BC (OGL-BC)](https://www2.gov.bc.ca/gov/content/data/open-data/open-government-licence-bc) -- [Affero General Public Licence (AGPL)](https://www.gnu.org/licenses/agpl-3.0.en.html) - ---- From f5bdc0d24157872dd81bed6b1626c81fa2838953 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Mon, 15 Dec 2025 15:52:30 -0800 Subject: [PATCH 03/52] Revise B.C. Developer Guide for clarity and structure Updated the B.C. Developer Guide to improve clarity and structure, including a new welcome section and streamlined content. --- docs/index.md | 80 ++++++++++++++------------------------------------- 1 file changed, 22 insertions(+), 58 deletions(-) diff --git a/docs/index.md b/docs/index.md index f04670a..a90de54 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,69 +1,33 @@ -## B.C. Developer Guide +# Welcome to B.C. Government -This document is a living guide to application development for the B.C government, updated regularly by the Developer Experience team. Written for all ministries, use it to guide your team's technical decisions and as a reference throughout the software lifecycle. +The B.C. Developer Guide **(BCDG)** offers B.C. Government developers a living guide to application development within the public service. Please use it as a reference throughout the software lifecycle, and technical decisions. -## Current Topics +The Developer Experience Team updates the BCDG. For any questions, concerns or feedback, we can be reached at developer.experience@gov.bc.ca. -### [Welcome to the B.C. government](./welcome-to-bc-gov/) +## 6 quick steps to get started -Helpful links and context for folks new to development within the government of B.C. +1. Bookmark this site because it serves as the central hub for development matters. +2. [Get access to the bcgov GitHub Organization](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/bc-government-organizations-in-github/#bcgov) + - This organization is B.C. Government's default storage for code. + - More information about `bcgov` and `bcgov-c` is available under [Organizations in GitHub](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/bc-government-organizations-in-github/#organizations-in-github) on the same page. +3. Get access to [GitHub Discussions](https://github.com/bcgov/bcgov-community-discussions). + - The developer community gathers here to ask questions, support each other with issues, and finds it the best source of support for internal serivces, such as cloud services and common components. +4. Explore [our internal services](https://digital.gov.bc.ca/technology/common-components/) and [Software-as-a-Service **(SaaS)** tools](https://digital.gov.bc.ca/technology/cloud/saas/) to support development. +5. Learn about what's happening in the [BC Gov Digital Ecosystem](https://digital.gov.bc.ca/blog/). +6. Bookmark the [Mobile Developer's Guide](https://developer.gov.bc.ca/docs/default/component/mobile-developer-guide/mobile-developer-guide-introduction/) for guidance on building mobile applications. -### [How To Select Technology](choosing-technology/how-to-select-technology.md) +### Security and compliance guidance and policies -This section shares some of the commonly adopted technologies to help teams make technical decisions for their projects. +Although we don't expect developers to memorize the guidance and policies below, we do expect developers to be aware of them: -### [GitHub in the B.C. government](./use-github-in-bcgov/bc-government-organizations-in-github/) +- [B.C. government OpenShift DevOps security considerations](https://developer.gov.bc.ca/docs/default/component/platform-developer-docs/docs/security-and-privacy-compliance/platform-security-compliance/) +- [BC Gov Policy for GitHub](https://github.com/bcgov/BC-Policy-Framework-For-GitHub/blob/master/README.md) +- [FOIPPA Quick Reference](https://raw.githubusercontent.com/bcgov/devhub-resources/master/resources/privacy/foippa_quick_reference.pdf) +- [IMIT standards](https://www2.gov.bc.ca/gov/content/governments/services-for-government/policies-procedures/im-it-standards) +- [Privacy and personal information in the B.C. public sector](https://www2.gov.bc.ca/gov/content/governments/services-for-government/information-management-technology/privacy) -GitHub is the preferred tool for B.C. government development team to store and share code. Learn about available options related to GitHub and how to license and manage code repositories. +#### Cloud Technology +We offer two options for cloud services: **private** and **public**. [Cloud Services](https://digital.gov.bc.ca/technology/cloud/) offers more information about both services. -### Developer Community Tools -#### [Rocket.Chat](rocketchat/steps-to-join-rocketchat.md) - -We use Rocket.Chat for technical discussions. It’s similar to Slack or Discord. - -Learn how to join and use Rocket.Chat and connect with other developers across the B.C. government. - -### Front End Development - -#### [Accessibility resources](accessibility-resources.md) - -Understand what resources are available to support the development of accessible web applications. - -#### [Design System](design-system/about-the-design-system.md) - -Learn what the BC Government Design System for Digital Services can do for your project. - -#### [Working with Data](working-with-data.md) - -Understand what B.C. Data Services support are available to support the success of technical projects. - -## Future Topics - -In the spirit of #Agile and #WorkingInTheOpen, we're taking an iterative approach to publishing new guidance. - -Potential topics for this guide include: - -- Digital Government 101 -- Ways of working in the B.C. government -- Supports for developers -- Developer communities -- Application lifecycle -- Deploying applications -- Testing applications -- Operating applications -- Licensing and intellectual property -- Code management -- Common code, components, and services -- Languages and frameworks -- Design -- Multilingual support -- Architecture -- Networking -- Security -- Compliance - -## Contact us - -This guide is owned and maintained by the Developer Experience team within the Digital Office. Please reach out with questions or feedback to [developer.experience@gov.bc.ca](mailto:developer.experience@gov.bc.ca). From e46ff3b9b5ce4a2f94f03fd734af5bb54a91ef75 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Mon, 15 Dec 2025 16:00:46 -0800 Subject: [PATCH 04/52] Update evaluate-open-source-content.md --- .../evaluate-open-source-content.md | 78 ++++++------------- 1 file changed, 22 insertions(+), 56 deletions(-) diff --git a/docs/use-github-in-bcgov/evaluate-open-source-content.md b/docs/use-github-in-bcgov/evaluate-open-source-content.md index bfa757b..b3d693a 100644 --- a/docs/use-github-in-bcgov/evaluate-open-source-content.md +++ b/docs/use-github-in-bcgov/evaluate-open-source-content.md @@ -1,79 +1,45 @@ ---- -title: Evaluate open-source content +# Evaluate open-source content -slug: evaluate-open-source-content +To prepare for open-source development, all teams must undergo an evaluation process of their content before posting anything onto `bcgov` or `bcgov-c` GitHub organizations. -description: Describes guidelines to evaluate open-source content and whether you can use it on GitHub. +We wrote guidelines below to help teams in four areas that can restrict open-source: -keywords: privacy, copyright, legal, contracts, policy, security, open-source, licence, license, GitHub, repository +* Privacy -page_purpose: Outlines the types of issues that could prevent a developer from using open-source content in their project and gives information on how to evaluate the content. +* Security -audience: technical lead, developer +* Copyright -author: Jonathan Bond +* Legal, contractual, and policy requirements -content_owner: Olena Mitovska/Nick Corcoran - -sort_order: 5 ---- - -# Evaluate open-source content - -Use the following guidelines to make sure that you are able to use existing, open-source content on GitHub. - -For more information on approval requirements, see [Start working in the BC Gov GitHub organization](start-working-in-bcgov-github-organization.md). - -## On this page -- [Privacy](#privacy) -- [Copyright](#copyright) -- [Legal, contractual, or policy](#legal-contractual-or-policy-constraints) -- [Security](#security) - -These guidelines help you make sure that there are no restrictions to using the material publicly. Restrictions may be due to one of the following concerns: - -- Privacy -- Copyright -- Legal, contractual or policy -- Security - -Evaluate the content you wish to use before posting the material in a GitHub repository. +The [First steps working in GitHub doc](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/start-working-in-bcgov-github-organization/) may also be of help because it has more information on conditions for approval. ## Privacy -Make sure that the content is free of personal information that may directly identify an individual (for example, name, phone number, photo, address, driver's licence number or any similar identification number). +Personal information **(PI)**, like name, phone number, photo, address, driver's license numbers, etc., must not be posted in public repos. -Ministries may contact Knowledge and Information Services to assist in privacy assessments. +Teams should contact their privacy analyst for help in privacy assessments. -## Copyright -Make sure to meet the following requirements: +## Security -- Content is created solely by B.C. government employees -- Content is fully owned by the B.C. government and doesn't contain any third-party content. Collect copies of any contracts related to the content for review with the [Intellectual Property Program (IPP)](https://www2.gov.bc.ca/gov/content/governments/services-for-government/policies-procedures/intellectual-property/intellectual-property-program) -- Content has no terms of use or exclusive licences that prohibit the Province from licensing the content on GitHub. Collect information concerning any terms of use or licences related to the content for review with the IPP -- You have [authority to license the content](license-your-github-repository.md) +Contact the Ministry Chief Information Security Officer **(MISO)** to make sure all mandatory security controls are implemented. -Ministries **must** contact the IPP to assist in this assessment. Any legal review or legal advice is provided by the Legal Services Branch. +Anything labelled **'public'** must meet the [Information Security Classification Framework](https://www2.gov.bc.ca/gov/content/governments/services-for-government/information-management-technology/information-security/information-security-classification). -## Legal, contractual or policy constraints +## Copyright -Make sure that the public release and use of the content is permitted under law, contract or policy. For example, make sure that there are no relevant legal, contractual or policy restrictions or limitations. +The requirements below are mandatory before posting on GH: -If there are legal, contractual or policy restrictions or limitations on the content, you must address them before you can use the content. +* Content is created only by B.C. government employees -## Security +* Content is owned by the B.C. government and doesn't have third-party content. Collect copies of contracts related to the content for review with the [Intellectual Property Program](https://www2.gov.bc.ca/gov/content/governments/services-for-government/policies-procedures/intellectual-property/intellectual-property-program) **(IPP)**. -Contact your [Ministry Information Security Officer (MISO)](https://www2.gov.bc.ca/gov/content/governments/services-for-government/policies-procedures/information-security-policy-and-guidelines/role-of-miso) to make sure that all necessary security controls have been implemented. +* Content doesn't have terms of use or exclusive licences that prohibit the Province from licensing the content on GitHub. Collect information about any terms of use or licences related to the content for review with the IPP. -Make sure that the material has been labelled **Public**, using the [Information Security Classification Framework](https://www2.gov.bc.ca/gov/content/governments/services-for-government/information-management-technology/information-security/information-security-classification). +* The team has authority to license the content. More information can be found on the [Licenses for GitHub repos doc](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/license-your-github-repository/). ---- -Related links: +Ministries must contact the IPP to assist in this assessment. The Legal Services branch offers legal review or advice. -- [Start working in the BCGov GitHub organization](start-working-in-bcgov-github-organization.md) -- [Intellectual Property Program (IPP)](https://www2.gov.bc.ca/gov/content/governments/services-for-government/policies-procedures/intellectual-property/intellectual-property-program) -- [License your GitHub repository](license-your-github-repository.md) -- [Ministry Information Security Officer (MISO)](https://www2.gov.bc.ca/gov/content/governments/services-for-government/policies-procedures/information-security-policy-and-guidelines/role-of-miso) -- [Information Security Classification Framework](https://www2.gov.bc.ca/gov/content/governments/services-for-government/information-management-technology/information-security/information-security-classification) +## Legal, contractual, and policy requirements ---- +The public release and use of content must be permitted under law, contract, or policy. Any and all ramifications of the content must be addressed beforehand. From 6ac0b2f04eb89575aa0457a6c219cc159b15b76f Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Mon, 15 Dec 2025 16:22:07 -0800 Subject: [PATCH 05/52] Revise guidelines for working in BCGov GitHub organization Updated the document to clarify processes for sharing code, initiating projects, and contributing to external repositories. Improved language for consistency and clarity throughout. --- ...rt-working-in-bcgov-github-organization.md | 88 ++++++++----------- 1 file changed, 38 insertions(+), 50 deletions(-) diff --git a/docs/use-github-in-bcgov/start-working-in-bcgov-github-organization.md b/docs/use-github-in-bcgov/start-working-in-bcgov-github-organization.md index f4d3f46..373deff 100644 --- a/docs/use-github-in-bcgov/start-working-in-bcgov-github-organization.md +++ b/docs/use-github-in-bcgov/start-working-in-bcgov-github-organization.md @@ -1,85 +1,73 @@ -# Start working in the BCGov GitHub organization +# First steps working in GitHub -If you plan to share code developed by or for the B.C. government, [evaluate the content](evaluate-open-source-content.md) and get approval from your deputy minister. Deputy ministers may choose to delegate this authority to ministry chief information officers (CIOs). +Teams planning to share code need to evaluate the content, and get approval from their Deputy Minister **(DM)**. A DM may delegate approval to a Ministry Chief Information Officer **(MCIO)**. -## On this page +The B.C. Government works in the open, using [open development practices](https://digital.gov.bc.ca/policies-standards/dcop/open/) which includes: -- [Post existing code or projects](#post-existing-code-or-projects) -- [Initiate new code or projects](#initiate-new-code-or-projects) -- [Contribute to outside code or projects](#contribute-to-outside-code-or-projects) +* **[Mandatory GitHub repo files](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/required-pages-for-github-repository/)** + - README file + - Contributing file + - Code of Conduct file + - License file. -The B.C. government follows the Open Development Standard, which outlines the following: - -* [Minimum content requirements](required-pages-for-github-repository.md): README, contributing file, code of conduct and license * Roles and responsibilities + * Basic mechanics of working in GitHub -Generally, GitHub projects fall under one of the three following categories, with different key considerations depending on the type. +## Three common ways to start working in GitHub -## Post existing code or projects +### Post existing code or projects -Projects like this follow two basic approaches, but can vary. +There are two common approaches a team can take: -* **Throw it over the wall**: You have code that you want to make available because it might be useful to others. However, you don't want to make an open-ended commitment to maintain an active open-source project. +* **Throw it over the wall:** code that can be made availabe to others, but teams shouldn't make an open-ended committement to keep an active open-source project. -* **Create and run a sustainable project**: You have code that you want to make available and then run as an active project: accepting patches, soliciting code contributions, adding new maintainers, participating in user and developer forums, doing regular releases and more. +* **Create and run a sustainable project:** code that can be made available, then run as an active project, inclusive of accepting patches, soliciting code contributions, adding new maintainers, participating in user and developer forums, doing regular releases and more. -In both cases, the basic steps to release the code are similar, while the implications for project management and resourcing are not. Key requirements in these scenarios include the following: +Both methods use similar ways to release the code. They differ in project management and resourcing. Key requirements in these scenarios include: -- Confirm your [authority to license](license-your-github-repository.md) +* Confirming team authority to license. - Choose an open-source license and consult with the Intellectual Property Program (IPP) to make sure government has the right to release the code. +* Choosing an open-source license, and consult with the Intellectual Property Program **(IPP)** to make sure government has the right to release the code. + * If using code from another open-source project, follow to the existing licensing provisions, and make sure the licences are compatiable. Per the [evaluate open-source content doc](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/evaluate-open-source-content/), don't infringe on intellectual property rights. These can include, patent rights, trademarks in the code or documentation. - If any of the code is from another open-source project, make sure you adhere to the existing licensing provisions and make sure the licence is compatible when you select a licence to apply to your project. +* Confirming that there are no restrictions on releasing the code or documentation imposed by legislation, policy or contracts. -- Make sure there are no other intellectual property considerations +* Checking for any dependencies + - Check library dependencies, sample or configuration data to make sure it's appropriate for release, or is separated. - These can include patent rights or trademarks in the code or documentation. Confirm that there are no restrictions on releasing the code or documentation imposed by legislation, policy or contracts. +Active project needs appropriate processes and terms to manage contributions. -- Assess any dependencies +### Integrating GitHub Apps - Check library dependencies, sample or configuration data to make sure it's appropriate for release or is separated out, if needed. +We get large volumes of asks about adding GitHub Apps to our org's repos. Request a GitHub App to be installed from the **BCDevOps Requests Issue: Request for integrating a GitHub App**. -If you are intending to maintain an active project, make sure to establish the appropriate processes and terms to manage contributions. +If the available applications don't work for the team, please create an issue. We need: -## Integrating GitHub Apps +* Contact information -We have large volumes of asks about adding GitHub Apps to our organization’s repository. Request a GitHub App to be installed from the BCDevOps Requests Issue: [Request for integrating a GitHub App](https://citz-do.atlassian.net/servicedesk/customer/portal/2/group/9/create/10). -If the existing applications don't work for you or your team, please create an issue. We need: +* Detailed information about the GitHub App -1. Your contact information -1. Detailed information about the GitHub App +### Initiate new code or projects +These types of projects fall under open-source and collaboration: -## Initiate new code or projects +* Choose an open-source licence and confirm team authority to license. -These are projects that you want to manage as an open-source, collaborative project. +* Use the [mandatory GitHub repo files doc](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/required-pages-for-github-repository/) to create the specified pages. -- Choose an open-source licence and confirm your [authority to license](license-your-github-repository.md) -- Determine how contributions are made and managed and include this information in the contributor file in the repository. -- [Create the minimum required content](required-pages-for-github-repository.md). -- Add a [Contributor Code of Conduct](http://contributor-covenant.org/) to your repository. This document lets people know that all are welcome to contribute, and that all who contribute pledge to make participation in the project a harassment-free experience for everyone. Include a code of conduct and provide a contact method (in the placeholder) so that people know how to report violations. Introduce the code of conduct in your `readme.md`. +## Contribute to external code or projects -## Contribute to outside code or projects +Sometimes, it's useful and appropriate for employees to contribute to non-B.C. Government repos as part of their workflow. In these cases, consider the following: -There may be circumstances where it's useful and appropriate for employees to contribute to non-B.C. government repositories as a part of their work. In these cases, consider the following: +* Any contribution, size, and scope is relevant. Team leads should confirm this. -- Make sure contributions are relevant, and the size and scope are consistent with your priorities. This may involve checking with your supervisor. -- Make sure the licensing provisions of the project you are contributing to are appropriate. For example, it's licensed under an OSI approved license and you aren't required to assign copyright to the project. +* Licensing provisions of the project must be appropriate. For example, it's licensed under an OSI approved license and no requirement to assign copyright to the project. - If the project requires you to sign a contributor agreement, get advice from Legal Services as to whether the terms are appropriate. +* If the project requires a contributor agreement to be signed, get advice from Legal Services if terms are appropriate. - If the project uses a reciprocal or "copyleft" license, such as GPL or Mozilla, make sure you understand the requirements for publishing any modifications you make to the code. +* If the project uses a reciprocal or "copyleft" license, such as GPL or Mozilla, understand the requirements for publishing any modifications to the code. -- Confirm your [authority to license](license-your-github-repository.md) +* Confirm team authority to license. Employees can also contribute to non-B.C. government owned intellectual property rights outside their professional roles by using their personal email linked to their GitHub account. - ---- -Related links: - -* [Evaluate the content](evaluate-open-source-content.md) -* [Required pages for a GitHub repository](required-pages-for-github-repository.md) -* [License your GitHub repository](license-your-github-repository.md) - ---- From cb93ab73144bfb5050b756cf43c8514540e49170 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Mon, 15 Dec 2025 16:29:29 -0800 Subject: [PATCH 06/52] Revise required pages for GitHub repository Updated the document to clarify required markdown files for BC Government repositories, including License, README, Code of Conduct, and Contributing guidelines. --- .../required-pages-for-github-repository.md | 84 ++++++------------- 1 file changed, 27 insertions(+), 57 deletions(-) diff --git a/docs/use-github-in-bcgov/required-pages-for-github-repository.md b/docs/use-github-in-bcgov/required-pages-for-github-repository.md index b04043e..198586e 100644 --- a/docs/use-github-in-bcgov/required-pages-for-github-repository.md +++ b/docs/use-github-in-bcgov/required-pages-for-github-repository.md @@ -1,80 +1,50 @@ ---- -title: Required pages for a GitHub repository +# Mandatory GitHub repo files -slug: required-pages-for-github-repository +The following markdown files are required in every `bcgov` repos: -description: Describes the pages that must be added to a project in the BC Government organization +* License file **(LICENSE.md)** +* README file **(README.md)** +* Code of Conduct file **(CODE_OF_CONDUCT.md)** +* Contributing guidelines file **(CONTRIBUTING.md)** -keywords: readme, contributor, code of conduct, best practices, repository, repository management, GitHub, working in GitHub, open source, working in the open +## License file -page_purpose: Discusses the pages that users should include in their repositories and gives guidelines on what those pages should provide +All repos need a license. Choose the best fit for the team repo. Important information about license types can be found on the [Licenses for GitHub repos doc](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/license-your-github-repository/). -audience: technical lead, developer +## README file -author: Jonathan Bond +Please read and adapt the [GH README guidelines](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes) and [5 tips for making your GitHub profile page accessible](https://github.blog/developer-skills/github/5-tips-for-making-your-github-profile-page-accessible/) for guidance to create good README files. Teams can find extensive documentation on GH about README files for repos. -content_owner: Olena Mitovska +Aside from GH documentation, please include: -sort_order: 7 ---- +* A brief project description. -# Required pages for a GitHub repository +* An overview of how to contribute to the team repo, and a link to repo contribution guidelines. -When you create a repository in the `bcgov` organization, add the following markdown files: +* Dependent on licence, boilerplate text. [Licenses for GitHub repos doc](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/license-your-github-repository/) offers more information about the topic. -- License -- README -- Code of conduct -- Contribution guidelines +* A link to team Code of Conduct file. -## On this page +Here's a [sample README file](https://github.com/bcgov/BC-Policy-Framework-For-GitHub/blob/master/BC-Gov-Org-HowTo/SAMPLE-README.md ). -- [Licence](#licence) -- [ReadMe](#readme) -- [Code of conduct](#code-of-conduct) -- [Contribution guidelines](#contribution-guidelines) +## Code of Conduct file -## Licence -Choose a licence and place a licence file in your repository before you do anything else. For important information on licences, see [License your GitHub repository](license-your-github-repository.md). +Code of Conducts fosters an open and welcoming environment, if written with clarity. -Depending on the licence you choose, add boilerplate text for the applicable licence to your README file. +Two starting points for creating a strong Code of Coduct: +* [Contributor Covenant](https://www.contributor-covenant.org/): common Code of Conduct for open source projects. -## ReadMe -GitHub has extensive documentation on how to create a good README file for your repository. Follow these guidelines when you create your README. +* [GitHub's guidelines on healthy contributions](https://docs.github.com/en/github/building-a-strong-community/setting-guidelines-for-repository-contributors): guidance on setting up a code of conduct for healthy contributions. -For more information, see [About READMEs](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes). +Here's a [sample Code of Conduct file](https://github.com/bcgov/BC-Policy-Framework-For-GitHub/blob/master/BC-Gov-Org-HowTo/SAMPLE-CODE_OF_CONDUCT.md). -Make sure to include the following: +## Contributing guidelines file -- A brief description of your project -- An overview on how to contribute to the repository with a link to your contribution guidelines -- Depending on your licence, boilerplate text for the applicable licence. For more information, see [License your GitHub repository](license-your-github-repository.md) -- A link to your code of conduct file +Always make sure contribution guidelines offer clarity and accurate methods of contributing to team repos. -See a [sample README file](https://github.com/bcgov/BC-Policy-Framework-For-GitHub/blob/master/BC-Gov-Org-HowTo/SAMPLE-README.md). +For example, if the repo needs contributors to fork the repo and submit pull requests, make sure it's included. Also, add links to the applicable documentation. -## Code of conduct -Write a clear code of conduct to ensure contributors to your project foster an open and welcoming environment. +Contributors should be aware of the repo license and relevant documentation. -Two good starting points to create a code of conduct for your project are the [Contributor Covenant](https://www.contributor-covenant.org/version/1/4/code-of-conduct/) and GitHub's guidelines on [healthy contributions](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions). +Here's a [sample contributing guildelines file.](https://github.com/bcgov/BC-Policy-Framework-For-GitHub/blob/master/BC-Gov-Org-HowTo/SAMPLE-CONTRIBUTING.md) -See a [sample code of conduct file](https://github.com/bcgov/BC-Policy-Framework-For-GitHub/blob/master/BC-Gov-Org-HowTo/SAMPLE-CODE_OF_CONDUCT.md). - -## Contribution guidelines -Write concise and clear contribution guidelines. Let potential contributors know how you prefer they work on projects and give them the correct information to do so. - -For example, if you prefer contributors fork repositories and [submit pull requests](https://help.github.com/articles/using-pull-requests/), provide links to the applicable documentation. - -Make sure you're clear on the licence that applies to your repository and provide a link to relevant documentation. - -See a [sample contributing file](https://github.com/bcgov/BC-Policy-Framework-For-GitHub/blob/master/BC-Gov-Org-HowTo/SAMPLE-CONTRIBUTING.md). - ---- -Related links: - -* [About READMEs](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes) -* [License your GitHub repository](license-your-github-repository.md) -* [Contributor Covenant](https://www.contributor-covenant.org/version/1/4/code-of-conduct/) -* [Healthy contributions](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions) -* [Using pull requests](https://help.github.com/articles/using-pull-requests/) ---- From c67fa0a6bb175c1ede2784a0a099d1cff6ca609f Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Mon, 15 Dec 2025 16:40:16 -0800 Subject: [PATCH 07/52] Clarify steps for removing user GitHub access Updated the document to clarify the steps for removing a user's GitHub access in BCGov, including the importance of IDIR account cancellation and the sequence of actions required. --- .../remove-user-bcgov-github-access.md | 39 ++++++------------- 1 file changed, 12 insertions(+), 27 deletions(-) diff --git a/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md b/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md index 6afc952..dc051f6 100644 --- a/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md +++ b/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md @@ -1,37 +1,22 @@ +# Removing member access from `bcgov` and `bcgov-c` -# Remove a user's BCGov GitHub access +Removing a member's access should only occur when members don't work for the government anymore or moved to a different role that doesn't need access. -There are two steps to remove a user: +We have two steps to remove access: +1. [Remove their access to team repos](https://docs.github.com/en/organizations/organizing-members-into-teams/removing-organization-members-from-a-team). -1. Remove their access to your repositories -1. Remove their membership in the [bcgov](https://github.com/bcgov) and [bcgov-c](https://github.com/bcgov-c) GitHub organizations +2. [Remove membership in `bcgov` and/or `bcgov-c` orgs](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person). -## Remove access to repositories -A user may access your repositories by GitHub team membership or direct access. +## Step 1: Remove access to team repos -Remove their access by: +A GH user can access a team repo via GitHub team membership, or direct repo access. The GitHub help pages below offers guidance on how to complete removal: -- [removing them from your GitHub team(s)](https://docs.github.com/en/organizations/organizing-members-into-teams/removing-organization-members-from-a-team) -- [removing them in your repository's "Collaborators & teams" setting](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person) +* [removing members from GitHub team(s)](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person) +* [removing members from repo "Collaborators & teams" setting](https://docs.github.com/en/organizations/organizing-members-into-teams/removing-organization-members-from-a-team) +## Step 2: Remove membership in `bcgov` and/or `bcgov-c` orgs -## Remove membership in GitHub organizations - - -!!! warning - Only do this step if the user is no longer an employee or contractor with the government. - -Membership in the [bcgov](https://github.com/bcgov) and [bcgov-c](https://github.com/bcgov-c) GitHub organizations is [controlled by IDIRs](github-transition-guide.md). - -A team's manager must [cancel a user's IDIR account](https://ociomysc.service-now.com/sp?id=kb_article&sys_id=5f3fab83db1a5690fa86193813961933) to remove them from the [bcgov](https://github.com/bcgov) and [bcgov-c](https://github.com/bcgov-c) GitHub organizations. - -IDIR cancellation may take a few days to complete. So, make sure to remove the user's access to your repositories ASAP. - -# Related Links - -* [GitHub - Removing organization members from a team](https://docs.github.com/en/organizations/organizing-members-into-teams/removing-organization-members-from-a-team) -* [GitHub - Managing teams and people with access to your repository](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository) -* [My Service Centre - Manage IDIR Access](https://ociomysc.service-now.com/sp?id=kb_article&sys_id=5f3fab83db1a5690fa86193813961933) - +The Developer Experience team doesn't remove membership from the `bcgov` and `bcgov-c` orgs. Membership is controlled by IDIRs, so a team's manager must [cancel a user's IDIR account on MySC](https://ociomysc.service-now.com/sp?id=kb_article&sys_id=5f3fab83db1a5690fa86193813961933). This makes sure users are removed, however, cancellation may take a few days. +Please remove the member's access from team repos immediately. From 63c02712f24edacf1334a28cbec29022c88f5aee Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Mon, 15 Dec 2025 16:42:42 -0800 Subject: [PATCH 08/52] Revise technology selection guidelines and structure Updated the document to reflect a more structured approach to selecting technology, including a clearer presentation of technology options and considerations for teams. Added sections on current technology options, development frameworks, hosting services, and technical considerations. --- .../how-to-select-technology.md | 102 ++++++++++-------- 1 file changed, 59 insertions(+), 43 deletions(-) diff --git a/docs/choosing-technology/how-to-select-technology.md b/docs/choosing-technology/how-to-select-technology.md index 8f5c6b5..eb4f53f 100644 --- a/docs/choosing-technology/how-to-select-technology.md +++ b/docs/choosing-technology/how-to-select-technology.md @@ -1,60 +1,76 @@ -# Selecting Technology for a B.C. Government System +# Choosing project technology -Selecting suitable technology is an important step in developing a system for the B.C. government and the teams and individuals involved in building new systems have the latitude to make choices about the technologies their systems will use. There is a wide range of technology currently in use within the systems built for and by the B.C government. The section below contains a cross-section of some of the technology options used within the B.C. government's growing portfolio of modern digital services, with links to relevant resources. +Every team and ministry has different needs. Choosing the suitable technology builds the foundation of excellent user experience. -## Technologies in use within B.C. government's modern systems +We offer a wide range of options within B.C. Government systems. The tables below show a cross-section of some technology that developers can use. Each option links to more information about it. -| Technology type | Examples or choices | -| -------------------------------------- |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Collaboration tools | [JIRA](https://www.atlassian.com/jira), [GitHub Issues](https://docs.github.com/en/issues), [ZenHub](https://www.zenhub.com), [Miro](https://miro.com/index/), [Mural](https://mural.co), [MS Teams](https://teams.microsoft.com), [Rocket.Chat](https://chat.developer.gov.bc.ca), [GitHub Discussions](https://github.com/bcgov/bcgov-community-discussions), [Loop](https://loop.cloud.microsoft) | -| Code and artifact management | [GitHub](https://github.com/bcgov), [Artifactory](http://artifacts.developer.gov.bc.ca/), [GitHub Packages](https://docs.github.com/en/packages) | -| Automation tools | [GitHub Actions](https://docs.github.com/en/actions), [ArgoCD](/docs/default/component/platform-developer-docs/docs/automation-and-resiliency/argo-cd-usage/), [Terraform](https://www.terraform.io), [Tekton/OpenShift Pipelines](/docs/default/component/platform-developer-docs/docs/automation-and-resiliency/cicd-pipeline-templates-for-private-cloud-teams/) | -| Common components | [Keycloak SSO](/docs/default/component/css-docs), [Digital Trust](https://digital.gov.bc.ca/digital-trust/home/), [BC Address Geocoder](https://digital.gov.bc.ca/bcgov-common-components/bc-address-geocoder/), [BC Route Planner](https://digital.gov.bc.ca/bcgov-common-components/bc-route-planner/), [Simple Map Kit](https://digital.gov.bc.ca/bcgov-common-components/simple-map-kit/), [Common Document Generation Service](https://digital.gov.bc.ca/bcgov-common-components/common-document-generation-service/), [Common Hosted Forms Service](https://digital.gov.bc.ca/bcgov-common-components/common-hosted-form-service/), [Common Hosted Email Service](https://digital.gov.bc.ca/bcgov-common-components/common-hosted-email-service/), [Common Object Management Service](https://digital.gov.bc.ca/bcgov-common-components/common-object-management-service/), [Design System](https://digital.gov.bc.ca/bcgov-common-components/design-system/) | -| Programming languages | [Python](https://github.com/bcgov?q=&type=all&language=python&sort=), [Javascript](https://github.com/bcgov?q=&type=all&language=javascript&sort=), [TypeScript](https://github.com/bcgov?q=&type=all&language=typescript&sort=), [Java](https://github.com/bcgov?q=&type=all&language=java&sort=), [R](https://github.com/bcgov?q=&type=all&language=r&sort=), [C#](https://github.com/bcgov?q=&type=all&language=c%23&sort=), [PHP](https://github.com/bcgov?q=&type=all&language=php&sort=) | -| Front-end frameworks | [React](https://react.dev), [Angular](https://angular.io), [Vue](https://vuejs.org) | -| Back-end frameworks | [Express](https://expressjs.com), [NestJS](https://nestjs.com), [Django](https://www.djangoproject.com), [Flask](https://flask.palletsprojects.com/en/3.0.x/), [.NET Core](https://dotnet.microsoft.com/en-us/), [Laravel](https://laravel.com) | -| API and data services | [API Gateway](https://digital.gov.bc.ca/bcgov-common-components/api-program-services/), [BC Data Catalogue](https://catalogue.data.gov.bc.ca) | -| Middleware and databases | PostgreSQL, MySQL, MongoDB, Kafka, Redis, NATS | -| Operations support and security tools | Sysdig, Uptime.com, Kibana, Splunk, [Vault](https://www.vaultproject.io) | -| Application hosting | [Learn about application hosting options](#application-hosting-services-options) | -### Determining suitability +## Current technology options -While there is a range of possible choices shown above, neither the categories nor the examples in the table above are exhaustive and inclusion in the list doesn't represent an endorsement or recommendation. Each team is responsible for doing its own analysis to determine the suitability of a technology for its needs and situation. The list below includes some important considerations that may be relevant to a team's technology choices. +Although there's numerous choices displayed, the table below isn't exhaustive, nor represents an endorsement of any particular option. Every team should do its own research before deciding which technology best suits their needs and context. -* [Open source considerations](../use-github-in-bcgov/evaluate-open-source-content/) -* [Considering procurement policies](https://www2.gov.bc.ca/gov/content/governments/policies-for-government/core-policy/policies/procurement) (for commercial options) -* [Privacy](https://www2.gov.bc.ca/gov/content/governments/services-for-government/information-management-technology/privacy/privacy-impact-assessments) and [Security](https://www2.gov.bc.ca/gov/content/governments/services-for-government/information-management-technology/information-security/security-threat-and-risk-assessment) implications. -* Requirements, guidance or policies from a team's ministry or sector central IT group (ISB/IMB) +Please note the following important considerations that can impact choices: +- [Core Policy and Procedures Manual **(CPPM)** Chapter 6: Procurement](https://www2.gov.bc.ca/gov/content/governments/policies-for-government/core-policy/policies/procurement) +- Information Management Branch **(IMB)** and/or Security Information Branch **(SIB)** requirements, policies or guidance. +- [Privacy and Security compliance](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/security/security-and-privacy-compliance-and-guidance/) +- [Open-source content evaluation](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/evaluate-open-source-content/) + +### Development Frameworks + +|Type| Choice| +|----| ------| +|Programming languages|[Python](https://github.com/bcgov?q=&type=all&language=python&sort=), [Javascript](https://github.com/bcgov?q=&type=all&language=javascript&sort=), [TypeScript](https://github.com/bcgov?q=&type=all&language=typescript&sort=), [Java](https://github.com/bcgov?q=&type=all&language=java&sort=), [R](https://github.com/bcgov?q=&type=all&language=r&sort=), [C#](https://github.com/bcgov?q=&type=all&language=c%23&sort=), [PHP](https://github.com/bcgov?q=&type=all&language=php&sort=) +|Back-end| [Express](https://expressjs.com/), [NestJS](https://nestjs.com/), [Django](https://www.djangoproject.com/), [Flask](https://flask.palletsprojects.com/en/2.2.x/), [.NET Core](https://dotnet.microsoft.com/en-us/apps/aspnet), [Laravel](https://laravel.com/) +|Front-end| [React](https://reactjs.org/), [Angular](https://angular.io/), [Vue](https://vuejs.org/)| +|Code and artifact management| [GitHub](https://github.com/bcgov), [Artifactory](http://artifacts.developer.gov.bc.ca/), [GitHub Packages](https://docs.github.com/en/packages) +|Automation tools| [GitHub Actions](https://github.com/features/actions), [ArgoCD](https://argoproj.github.io/argo-cd/), [Terraform](https://www.terraform.io/), [Tekton/OpenShift Pipelines](https://tekton.dev/) + +### Hosting and operations +|Type| Choice| +|----| ------| +|Operations support and security| Sysdig, StatusCake, Loki, Splunk, [Vault](https://www.vaultproject.io) +|Application hosting| [Learn about application hosting options](#application-hosting-services-options) + + +### Collaboration +|Type| Choice| +|----| ------| +|Collaboration tools| [JIRA](https://www.atlassian.com/software/jira), [GitHub Discussions](https://github.com/features/discussions), [GitHub Issues](https://github.com/features/issues), [MS Teams](https://www.microsoft.com/en-ca/microsoft-teams/group-chat-software), [Loop](https://www.microsoft.com/en-us/microsoft-365/loop) +|Common Components| [Digital Trust](https://digital.gov.bc.ca/digital-trust/home/), [Keycloak SSO](docs/default/component/css-docs),[Design System](https://digital.gov.bc.ca/bcgov-common-components/design-system/), [Common Document Generation Service](https://digital.gov.bc.ca/bcgov-common-components/common-document-generation-service/), [Common Hosted Forms Service](https://digital.gov.bc.ca/bcgov-common-components/common-hosted-form-service/), [Common Hosted Email Service](https://digital.gov.bc.ca/bcgov-common-components/common-hosted-email-service/), [Common Object Management Service](https://digital.gov.bc.ca/bcgov-common-components/common-object-management-service/), [BC Address Geocoder](https://digital.gov.bc.ca/bcgov-common-components/bc-address-geocoder/), [BC Route Planner](https://digital.gov.bc.ca/bcgov-common-components/bc-route-planner/), [Simple Map Kit](https://digital.gov.bc.ca/bcgov-common-components/simple-map-kit/) + + +### Integration and data +|Type| Choice| +|----| ------| +|API and data services| [API Gateway](https://digital.gov.bc.ca/bcgov-common-components/api-program-services/), [BC Data Catalogue](https://catalogue.data.gov.bc.ca) +|Middleware and databases| PostgreSQL, MySQL, MongoDB, Kafka, Redis, NATS ## Application hosting services options -As a technical team, you can use this guide to help you and your team choose the best hosting platform for your product. +Each service offers unique features and capabilities that creates a secure and compliant environment for digital service hosting. Only services supported by Connected Services B.C. **(CSBC)** are listed: -Each service has unique capabilities and features that create a secure and compliant environment for digital service hosting. +- **Data centre: traditional hosting**: offers traditional managed hosting services for virtual and physical systems. It supports numerous operating systems and techonologies. + +- **Private Cloud: Red Hat OpenShift**: combines on-premise and cloud benefits. It offers a self-serve, secure, indepedent and scalable platform for hosting applications. -- The Data centre traditional hosting hosting offers traditional managed hosting services for virtual and physical systems. It supports various operating systems and technologies -- The Private cloud OpenShift platform combines on-premise and cloud benefits. It offers managed services on dedicated hardware for control and flexibility -- The Public cloud Amazon Web Services (AWS) Landing Zone uses AWS hardware. It provides scalable, on-demand computing services accessed through the internet with a secure, pre-configured environment +- **Public Cloud: Amazon Web Services (AWS) and Azure**: offers Enterprise support from AWS and Azure, a centralized and supported environment, rapid scalability, and simplified procurement. -*Notes:* +- **Software as a Service (SaaS)**: offers ready-to-use software applications, hosted and managed by third-party providers. -- Only services that are managed by OCIO are listed -- If you’re considering the adoption of ready-to-use, subscription-based software, visit Software as a Service (SaaS) -- Contact the OCIO Enterprise Architecture team at citzas@gov.bc.ca if you need guidance +Technical teams can use the table below compares the three to help choose the best hosting platform for their product. -### Hosting technical considerations +**Application hosting services comparison table** -For more information on Cloud hosting options available to you, please see the [Cloud Smart](https://digital.gov.bc.ca/policies-standards/cloud-smart/) documentation. +Column 1 lists features, column 2 has Data centre traditional hosting features, column 3 has Private cloud OpenShift platform features, and column 4 has Public cloud Azure and AWS Landing Zones features. -| | Data centre traditional hosting | [Private cloud OpenShift platform](/docs/default/component/platform-developer-docs) | [Public cloud Azure & AWS Landing Zones](/docs/default/component/public-cloud-techdocs) | +| | Data centre traditional hosting | [Private cloud OpenShift platform](docs/default/component/platform-developer-docs) | [Public cloud Azure and AWS Landing Zones](docs/default/component/public-cloud-techdocs) | |---|--------------------------------------|-----------------------------------|--------------------------------| -| **Is this service recommended for business mission critical applications?** | Yes | Yes | No | -| **What type of hosting environment does this service offer?** | Virtual machines and physical hardware | Containerized | Containerized and serverless | -| **What’s the highest [data classification](https://www2.gov.bc.ca/assets/gov/government/services-for-government-and-broader-public-sector/information-technology-services/standards-files/618_information_security_classification_standard.pdf) this platform can host?** | Protected C | Protected B and Protected C | Protected B | -| **How can you provision hosting space?** | [iStore order](https://ssbc-client.gov.bc.ca/order/istore.htm) | [Self-serve online](https://registry.developer.gov.bc.ca/login) | [Self-serve online](https://registry.developer.gov.bc.ca/login) | -| **How elastic is this service? Can it scale up to meet increased demand?** | Low
Computer resource must be pre-purchased to be available | Medium / High
Elasticity ensures that a project can scale its resource usage up to the maximum allowed by the project resource quota
Learn more about OpenShift project resource quotas | High
Elasticity can scale as needed, limited only by the product budget
Learn more about AWS Landing Zone | -| **What additional services are available?** | - Software Defined Network
- S3 Object Store | - Software Defined Network
- S3 Object Store
- AI/ML
- Security tools | - Checkpoint CSPM
- All AWS IaaS/PaaS services available in Canada central region (ca-central-1) and United States east coast (us-east-1). Does not include Marketplace services | -| **Internal and external expertise availability** | High
Extensive expertise within OCIO | High
Extensive expertise within OCIO | Medium
OCIO is developing expertise to support clients | -| **Recommended technical skillset** | - Server administration
- Security operations
- Technical architecture
- Application development
- Database administration | - DevOps
- Full-stack development
- Site reliability engineering
- Security operations
- Database administration | - DevOps
- Full-stack development
- Site reliability engineering
- Security operations
- Technical architecture
- Network and infrastructure operations
- Database administration | -| **What amount of support is assigned to a product team?** | [Review shared responsibility model](https://digital.gov.bc.ca/technology/cloud/hosting-services/#shared) |[Review shared responsibility model](https://digital.gov.bc.ca/technology/cloud/hosting-services/#shared)|[Review shared responsibility model](https://digital.gov.bc.ca/technology/cloud/hosting-services/#shared)| \ No newline at end of file +|Recommended for mission critical applications |Yes|Yes|No| +|Recommended technical skillset|
  • Server administration
  • Security operations
  • Technical architecture
  • Application development
  • Database administration |
  • DevOps
  • Full-stack development
  • Site reliability engineering
  • Security operations
  • Database administration |
  • DevOps
  • Full-stack development
  • Site reliability engineering
  • Security operations
  • Technical architecture
  • Network and infrastructure operations
  • Database administration | +|Hosting environment|Virtual machines and physical hardware| Containerized|Containerized and serverless| +|Highest [data classification](https://www2.gov.bc.ca/assets/gov/government/services-for-government-and-broader-public-sector/information-technology-services/standards-files/618_information_security_classification_standard.pdf) | Protected C|Protected B and C|Protected B| +| Procurement | [iStore order](https://ssbc-client.gov.bc.ca/order/istore.htm) | [Self-serve online](https://registry.developer.gov.bc.ca/login) | [Self-serve online](https://registry.developer.gov.bc.ca/login) | +| Elasticity and scalability |
  • Low
  • Resource must be pre-purchased |
  • Medium - High
  • Maximum allowed by project resource quota |
  • High
  • Scale as needed, limited only by product budget| +|Additional services|
  • Software Defined Network
  • S3 Object Store |
  • Software Defined Network
  • S3 Object Store
  • AI/ML
  • Security tools |
  • Checkpoint CSPM
  • All AWS IaaS/PaaS services available in Canada central region (ca-central-1) and United States east coast (us-east-1).
  • Does not include Marketplace services | +|Expertise available|
  • High
  • Extensive expertise within CSBC |
  • High
  • Extensive expertise within CSBC |
  • Medium
  • CSBC is developing expertise to support clients | +| Support assigned to product team| [Review shared responsibility model](https://digital.gov.bc.ca/technology/cloud/hosting-services/#shared) |[Review shared responsibility model](https://digital.gov.bc.ca/technology/cloud/hosting-services/#shared)|[Review shared responsibility model](https://digital.gov.bc.ca/technology/cloud/hosting-services/#shared)| From f66db83a8dbedb40a71c6fcf782847cc368fc36c Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Wed, 17 Dec 2025 10:43:43 -0800 Subject: [PATCH 09/52] Revise GitHub transition guide for IDIR and SSO clarity Updated the GitHub transition guide to clarify IDIR usage and SSO processes. Added details on IDIR types, expiry management, and the transition from outside collaborators to full members. --- .../github-transition-guide.md | 100 +++++++----------- 1 file changed, 41 insertions(+), 59 deletions(-) diff --git a/docs/use-github-in-bcgov/github-transition-guide.md b/docs/use-github-in-bcgov/github-transition-guide.md index 6f8d4fe..0fcc9c5 100644 --- a/docs/use-github-in-bcgov/github-transition-guide.md +++ b/docs/use-github-in-bcgov/github-transition-guide.md @@ -1,8 +1,16 @@ -# Transition Guides +# Transition Guides for GitHub SSO + +The [B.C. Government organizations in GitHub doc](bc-government-organizations-in-github.md#single-sign-on) has an overview of SSO. Please read that section before reading these transition guides because the guides are supplementary material. + +The transition guide doc hosts two guides: + +- [**IDIR Guide**](#idir-guide): more detailed information about IDIRs and how they relate to the mandatory SSO feature on `bcgov` and `bcgov`. + +- [**Technical Guide**](#technical-guide): helps GitHub users prepare for the SSO feature, and confirms if users completed joining successfully + + If there’s a topic isn’t covered in the guide, please [submit a support request on JSM](https://citz-do.atlassian.net/servicedesk/customer/portal/2). -The IDIR guide offers more detailed information about IDIRs and how they relate to the mandatory SSO feature on 'bcgov' and 'bcgov-c'. If there’s a topic isn’t covered in the guide, please submit a ticket on our [service manager](https://citz-do.atlassian.net/servicedesk/customer/portal/2). -We published an SSO overview [on DevHub](bc-government-organizations-in-github.md#single-sign-on-is-coming-to-the-bc-governments-github-organizations). ## IDIR Guide @@ -15,19 +23,20 @@ Our organization has many different types of IDIRs, such as: - Generic IDIRs linked to shared inboxes - Contractor IDIRs -For SSO, we focus on 2 types of IDIRs: +For SSO, we use 2 types: - Primary IDIRs for employees - Contractor IDIRs ### Primary IDIRs for employees -B.C. Government employees have the default configuration compatible with SSO. [DevHub has instructions to link your IDIR to GitHub](bc-government-organizations-in-github.md#single-sign-on-is-coming-to-the-bc-governments-github-organizations). +B.C. Government employees have the default configuration compatible with SSO. The [B.C. Government organizations in GitHub doc's SSO section](bc-government-organizations-in-github.md#single-sign-on-is-coming-to-the-bc-governments-github-organizations) has instructions to link an IDIR to GitHub IDs. ### Compatible IDIRs for contractors -If a user is a contracted worker, then the process may be more complex depending on IDIR types. The table below gives an overview between P2 and E5, IDIRs compatible with the GitHub SSO feature. -We don’t foresee any technical issues with SSO if contractors have either IDIR type. If this isn’t the case, please fill out a form to open a ticket on [service manager](https://citz-do.atlassian.net/servicedesk/customer/portal/2). +If a user is a contracted worker, the process may be more complex depending on IDIR types. The table below gives an overview between P2 and E5 IDIRs. +We don’t foresee any technical issues with SSO if contractors have either IDIR type. If this isn’t the case, please [submit a support request on JSM](https://citz-do.atlassian.net/servicedesk/customer/portal/2). -P2 and E5 IDIR comparison +#### P2 and E5 IDIR comparison table + Column 1 lists IDIR features, column 2 has P2 features, and column 3 has E5 features. @@ -40,14 +49,19 @@ Column 1 lists IDIR features, column 2 has P2 features, and column 3 has E5 feat Please see [Service Bulletin 1350](https://ociomysc.service-now.com/sp?id=kb_article&sys_id=7a69f65fdbff9d10fa86193813961978&spa=1) for more information. -Contract managers must keep expiry dates updated because our team doesn’t have the ability to submit orders on behalf of ministries. - It’s very likely contractors already with IDIRs have P2. If linking doesn't work, please call 7-7000 or open a ticket to confirm through [MyService Centre](https://ociomysc.service-now.com/sp?id=ocio_sr_incident_management). - + +#### IDIR expiry + +Government employees don’t have expiry dates on their IDIR. Contractor IDIRs do. + +Once a contractor IDIR expires, the contractor loses general access. Contract managers must keep expiry dates updated. Our team doesn’t have the ability to submit orders on behalf of ministries. + + ### Contractors without IDIRs Each ministry has an authorized user who submits orders in [MyService Centre](https://ociomysc.service-now.com/sp?id=ocio_sr_incident_management). Please reach out to them as soon as possible to order an IDIR. -## Multiple IDIRs. +## Multiple IDIRs Developers with multiple IDIRs can join their most permanent IDIR to their GitHub ID. They can change IDIRs at any time. We tested and can confirm that users make changes on their own. @@ -56,13 +70,15 @@ The important things to keep in mind are: - The IDIR must not be expired - Our team cannot manage IDIR expiry dates -If you don’t see information that could be helpful on this guide, please let us know through [our service manager](https://citz-do.atlassian.net/servicedesk/customer/portal/2). +If you don’t see information that could be helpful on this guide, please let us know through [submit a support request on JSM](https://citz-do.atlassian.net/servicedesk/customer/portal/2). -## Technical Guide +#### P2 IDIR login -Our technical guide helps GitHub users prepare for the SSO feature, and confirms if users completed joining successfully. [Our IDIR guide](#idir-transition-guide) offers more details about IDIRs. +Vendors using both **P2 IDIRs** and external emails (e.g. ggg123@gmail.com) must log in with **\@gov.bc.ca**. + +## Technical Guide -Users cannot access the bcgov GitHub organization if they don't join their GitHub ID and IDIR. There are mechanisms in the system that force an IDIR login when you use your GitHub to login. +Users cannot access the `bcgov` nor `bcgov-c` GitHub organization if they don't join their IDIR and GitHub ID. There are mechanisms in the system that force an IDIR login when using GitHub to login. ### Validating authentication @@ -74,10 +90,10 @@ GitHub doesn't offer users a screen to confirm authentication. There are 2 alter 2) Another way to validate joining: -> 1. (**Mandatory step**) Go to https://github.com/bcgov/ -> 2. Got to your profile by clicking your avatar on the top right -> 3. Click "Settings" -> 4. Click "[Sessions](https://github.com/settings/sessions)" +> 1. (**Mandatory step**) Go to the [`bcgov`](https://github.com/bcgov/) org. +> 2. Go to your profile by clicking your avatar on the top right. +> 3. Click "Settings". +> 4. Click "[Sessions](https://github.com/settings/sessions)". > 5. Click "See more" button for the current web session > 6. If you're authenticated, GitHub will show details of your current session, inclusive of your device, your last login location, and when you last signed in. Clicking on the three dots by the "Your session expires" section will display the NameID from the linked IDIR. We've included a screenshot as an example: @@ -86,53 +102,19 @@ GitHub doesn't offer users a screen to confirm authentication. There are 2 alter ### Outside Collaborators -Government employees and contractors can be outside collaborators. We're ending the option to add [outside collaborators](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/adding-outside-collaborators-to-repositories-in-your-organization). GitHub will send invitations to current outside collaborators to become full members on 'bcgov', and IDIRs are needed. If you need an IDIR, please follow the instructions on [our IDIR guide](#idir-transition-guide). +We discontinued the option to add [outside collaborators](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/adding-outside-collaborators-to-repositories-in-your-organization). GitHub will send invitations to current outside collaborators to become full members on `bcgov`, and IDIRs are needed. -Accessess will stay the same. +To create IDIRs or have more information, please read [the IDIR guide](#idir-transition-guide). -## ZenHub - -If you lost access to ZenHub during linking, please follow these directions to re-authenticate: - -1. Log out of Zenhub -1. Revoke Zenhub as an authorized OAuth app from your GitHub account. - 1. Refer to [GitHub's documentation for details on how to revoke an OAuth app](https://docs.github.com/en/apps/oauth-apps/using-oauth-apps/reviewing-your-authorized-oauth-apps). -1. Log out of GitHub -1. Clear browser cache and cookies -1. Completely close and reopen your browser -1. Log back into GitHub -1. Log back into Zenhub using "Continue with Github" - -If needed, Zenhub has [more support](https://help.zenhub.com/support/solutions/articles/43000636925-re-authenticating-zenhub-if-your-team-is-using-saml) available. - -### IDIRs - -### P2 IDIR login - -Vendors using both **P2 IDIRs** and external emails (e.g. ggg123@gmail.com) must log in with **\@gov.bc.ca**. - -#### IDIR expiry - -Government employees don’t have expiry dates on their IDIR, only contractor IDIRs do. If you’re a contractor and your IDIR expires, then you won’t have general access anymore. Each ministry must manage contractor IDIRs because our team doesn’t have the capability to change expiry dates. - -[Our guide about IDIRs](#idirs) has more relevant information. - -#### Multiple IDIRs - -Developers with multiple IDIRs can link their most permanent IDIR to their GitHub ID. They can change IDIRs at any time. We tested and can confirm that users make changes on their own. - -The important things to keep in mind are: - -- The IDIR must not be expired -- The Developer Experience team cannot manage IDIR expiry dates for teams +Accessess will stay the same. ### No new GitHub ID needed GitHub differs from other tools that use IDIR as the user account to access services. -The reason is due to GitHub’s open source code community ecosystem. A part of our commitment to open government is the bcgov GitHub organization. We set up GitHub accounts to be associated with many different repositories and organizations because throughout their careers, developers contribute to many different open projects and organizations. +The reason is due to GitHub’s open source code community ecosystem. A part of our commitment to open government is the `bcgov` GitHub org. We set up GitHub accounts to be associated with many different repos and orgs because throughout their careers, developers contribute to many different open projects and organizations. -With the GitHub SSO upgrade, contractors and developers working in the bcgov GitHub organization will continue to use their GitHub to login to access GitHub. The extra step is the prompt to login to IDIR to comply with security policies. +With the GitHub SSO upgrade, contractors and developers working in the `bcgov` GitHub org will continue to use their GitHub to login to access GitHub. The extra step is the prompt to login to IDIR to comply with security policies. ### Resetting GitHub Keys From 7ba69bee57d8a17b84ec91a649528a097aa1d3e9 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Thu, 18 Dec 2025 09:55:55 -0800 Subject: [PATCH 10/52] Delete docs/use-github-in-bcgov/github-enterprise-user-licenses-bc-government.md (#89) Deleting page irrelevant page with outdated information. --- ...-enterprise-user-licenses-bc-government.md | 63 ------------------- 1 file changed, 63 deletions(-) delete mode 100644 docs/use-github-in-bcgov/github-enterprise-user-licenses-bc-government.md diff --git a/docs/use-github-in-bcgov/github-enterprise-user-licenses-bc-government.md b/docs/use-github-in-bcgov/github-enterprise-user-licenses-bc-government.md deleted file mode 100644 index 51811d6..0000000 --- a/docs/use-github-in-bcgov/github-enterprise-user-licenses-bc-government.md +++ /dev/null @@ -1,63 +0,0 @@ -# B.C. government GitHub Enterprise - ->Note: This page is under review as of December 2023 and will be updated for clarity and accuracy early in 2024. - -All code built for B.C. government for staff or contracted developers should be open source by default and stored in the public [`bcgov` organization on GitHub.com](https://github.com/bcgov). If you have closed source code and still want to use GitHub's functionality, you can store your code in a private repository within the B.C. government's [GitHub Enterprise environment](https://github.com/enterprises/bcgov-ent/). This page contains details related to that environment and its use. - -For more information about B.C. government GitHub organizations outside of GitHub Enterprise, see [B.C. government organizations in GitHub](bc-government-organizations-in-github.md). - -## B.C. government GitHub Enterprise Overview - -GitHub Enterprise offers various features beyond those of the Free and Teams tiers. To find out more about the features of GitHub Enterprise, you may wish to review [GitHub's product page](https://github.com/enterprise). - -There are certain notable differences between the [public facing `bcgov` GitHub organization](https://github.com/bcgov) and B.C. government's GitHub Enterprise environment. For example, the ability to create public repositories is disabled within GitHb Enterprise since with B.C. government public open source code should be in the [public `bcgov` organization](https://github.com/bcgov). - -Other details of GitHub Enterprise include the following: - -* Single sign-on is provided via Azure AD (aka Entra ID) -* Login uses government-issued IDIR identities -* Users will be automatically assigned new GitHub IDs, which will change the login experience for users working in both GitHub.com repositories and B.C. government GitHub Enterprise -* GitHub Actions is enabled -* Code Dependency Insights is enabled - -## GitHub Enterprise account ownership - -The B.C. government's GitHub Enterprise account is managed centrally by the Digital Office's [Developer Experience Team](mailto:developer.experience@gov.bc.ca). Ministries or sectors are provided with GitHub "organizations" within the central GitHub Enterprise account. Teams' private repositories are created within these organizations. Management of ministry or sector organizations within GitHub Enterprise is delegated to staff within the corresponding IMB/ISB. - -Paid licenses are required to use GitHub Enterprise. Licenses must be purchased for each user that will use or administer to the B.C. government GitHub Enterprise organizations or repositories. Each ministry or sector is responsible for acquiring and paying for its own licenses. The process for acquiring licences is described [below](#background-bc-government-github-enterprise-process-map). - -## Acquiring GitHub Enterprise user licences - -> Note: the process outlined below may be slightly different for some sectors or ministries, but it will be generally similar for all. For example, in some areas, the responsibility for interacting with CSAM may be done by the ministry or sector IMB/ISB staff rather than end users in a business area. - -This section outlines what is involved in acquiring the licenses required to use B.C. government GitHub Enterprise. - -### Pre-requisites: - -- Confirm that your intended use of GitHub Enterprise aligns with its purpose, which is exclusively for storing code that can't be, or isn't currently, open source. -- Confirm whether your ministry or sector is using GitHub Enterprise and know who in your IMB/ISB is responsible for managing access. If you aren't sure who to contact within your IMB/ISB, please contact the [Developer Experience Team](mailto:developer.experience@gov.bc.ca) for assistance. -- Identify who is responsible within your business area for submitting iStore orders. - -### Steps - -Once you've completed the pre-requisites, follow the steps below to acquire GitHub Enterprise licenses. - -- Request a quote via email to [SoftwareCentral.Management@gov.bc.ca](mailto:SoftwareCentral.Management@gov.bc.ca). Use the subject line "Request for Quotation for GitHub Enterprise" and indicate in the body the number of users who need GitHub Enterprise licenses. For example, "Could I please get a quote for 10 GitHub Enterprises licenses (Standalone)?". -- Wait for a response by email from CSAM, which will include a quote number and the associated cost for your licenses. This should take 2-3 business days. -- Work with the person reponsisble for iStore orders in your business area to create and submit an iStore order referencing the quote number to initiate the purchase. This will triggerthe e-approval process. -- Wait for a notification from CSAM indicating that they have made the purchase of GitHub licenses on your behalf. This should take less than 5 business days. Billing back to your expense authority will commence at this point. Billing occurs monthly until you notify CSAM to cancel the user licenses. -- Work with the appropriate individual or team within your ministry or sector IMB/ISB to request access to the corresponding organization within B.C. government's GitHub Enterprise environment. - -Once the above steps are complete, you'll be able to log in (using your IDIR) to the B.C. government GitHub Enterprise at [https://github.com/enterprises/bcgov-ent/](https://github.com/enterprises/bcgov-ent/) and begin working in private repositories within your ministry or sector's organization. - -## Background: BC government GitHub Enterprise process map - -The [Developer Experience Team](mailto:developer.experience@gov.bc.ca) has created the artifact below which captures the steps and teams involved in acquiring and mananaging GitHub Enterprise licenses. This version is intended for reference only. - -![A detailed diagram illustrating the process of acquiring and administering GitHub Enterprise licenses within the B.C. government. ](../images/github-e-process-map.png) ---- -Related links: - -* [BC Government Organizations in GitHub](bc-government-organizations-in-github.md) - ---- From 92ff275d01beac06e3d504bf5e39307df6857fe2 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 11:50:47 -0800 Subject: [PATCH 11/52] Revise introduction and enhance quick start steps Updated the introduction and added new steps for getting started with the Developer Guide. --- docs/index.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/docs/index.md b/docs/index.md index a90de54..fbdf5f1 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,20 +1,21 @@ # Welcome to B.C. Government -The B.C. Developer Guide **(BCDG)** offers B.C. Government developers a living guide to application development within the public service. Please use it as a reference throughout the software lifecycle, and technical decisions. +The B.C. Developer Guide **(BCDG)** offers B.C. Government developers a living guide to application development within the public service. Please use it as a reference throughout the software lifecycle, and technical decisions. -The Developer Experience Team updates the BCDG. For any questions, concerns or feedback, we can be reached at developer.experience@gov.bc.ca. +The Developer Experience Team updates the BCDG. We've embedded links into our content to facilitate learning. For any questions, concerns or feedback, we can be reached at developer.experience@gov.bc.ca. -## 6 quick steps to get started +## 7 quick steps to get started -1. Bookmark this site because it serves as the central hub for development matters. -2. [Get access to the bcgov GitHub Organization](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/bc-government-organizations-in-github/#bcgov) +1. Bookmark the Developer Guide because it serves as the central hub for development matters. +2. [Bookmark the Mobile Developer's Guide](https://developer.gov.bc.ca/docs/default/component/mobile-developer-guide/mobile-developer-guide-introduction/) for guidance on building mobile applications. +3. [Get access to the bcgov GitHub Organization](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/bc-government-organizations-in-github/#bcgov) - This organization is B.C. Government's default storage for code. - More information about `bcgov` and `bcgov-c` is available under [Organizations in GitHub](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/bc-government-organizations-in-github/#organizations-in-github) on the same page. -3. Get access to [GitHub Discussions](https://github.com/bcgov/bcgov-community-discussions). +4. [Bookmark the Developer Experience Jira Service Management](https://citz-do.atlassian.net/servicedesk/customer/portal/2) system, which is shortened to JSM. Users can submit support tickets +5. [Get access to GitHub Discussions](https://github.com/bcgov/bcgov-community-discussions). - The developer community gathers here to ask questions, support each other with issues, and finds it the best source of support for internal serivces, such as cloud services and common components. -4. Explore [our internal services](https://digital.gov.bc.ca/technology/common-components/) and [Software-as-a-Service **(SaaS)** tools](https://digital.gov.bc.ca/technology/cloud/saas/) to support development. -5. Learn about what's happening in the [BC Gov Digital Ecosystem](https://digital.gov.bc.ca/blog/). -6. Bookmark the [Mobile Developer's Guide](https://developer.gov.bc.ca/docs/default/component/mobile-developer-guide/mobile-developer-guide-introduction/) for guidance on building mobile applications. +6. Explore [our internal services](https://digital.gov.bc.ca/technology/common-components/) and [Software-as-a-Service **(SaaS)** tools](https://digital.gov.bc.ca/technology/cloud/saas/) to support development. +7. Learn about what's happening in the [BC Gov Digital Ecosystem](https://digital.gov.bc.ca/blog/). ### Security and compliance guidance and policies From 93c7125496901eba9a4d7a43ad8aca72b9ec629a Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 15:06:26 -0800 Subject: [PATCH 12/52] Improve clarity and update technology selection guide Revised language for clarity and consistency throughout the document. Updated links and descriptions for technology options and hosting services. --- .../how-to-select-technology.md | 38 +++++++++++-------- 1 file changed, 23 insertions(+), 15 deletions(-) diff --git a/docs/choosing-technology/how-to-select-technology.md b/docs/choosing-technology/how-to-select-technology.md index eb4f53f..4c04909 100644 --- a/docs/choosing-technology/how-to-select-technology.md +++ b/docs/choosing-technology/how-to-select-technology.md @@ -2,21 +2,22 @@ Every team and ministry has different needs. Choosing the suitable technology builds the foundation of excellent user experience. -We offer a wide range of options within B.C. Government systems. The tables below show a cross-section of some technology that developers can use. Each option links to more information about it. +We offer many options within B.C. Government systems. The tables below show a cross-section of some technology that developers can use. Users can click each option to get more information about it. ## Current technology options -Although there's numerous choices displayed, the table below isn't exhaustive, nor represents an endorsement of any particular option. Every team should do its own research before deciding which technology best suits their needs and context. +Although there's numerous choices, the options in the table below isn't exhaustive, nor represents an endorsement of any particular choice. Every team should do its own research before deciding which technology best suits their needs and context. -Please note the following important considerations that can impact choices: +Please note the following important considerations: -- [Core Policy and Procedures Manual **(CPPM)** Chapter 6: Procurement](https://www2.gov.bc.ca/gov/content/governments/policies-for-government/core-policy/policies/procurement) +- The [Core Policy and Procedures Manual **(CPPM)** Chapter 6: Procurement](https://www2.gov.bc.ca/gov/content/governments/policies-for-government/core-policy/policies/procurement) - Information Management Branch **(IMB)** and/or Security Information Branch **(SIB)** requirements, policies or guidance. - [Privacy and Security compliance](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/security/security-and-privacy-compliance-and-guidance/) -- [Open-source content evaluation](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/evaluate-open-source-content/) +- Our [open-source content evaluation doc](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/evaluate-open-source-content/) ### Development Frameworks +Column 1 lists the technology type. Column 2 lists the choices under that type. |Type| Choice| |----| ------| @@ -27,6 +28,8 @@ Please note the following important considerations that can impact choices: |Automation tools| [GitHub Actions](https://github.com/features/actions), [ArgoCD](https://argoproj.github.io/argo-cd/), [Terraform](https://www.terraform.io/), [Tekton/OpenShift Pipelines](https://tekton.dev/) ### Hosting and operations +Column 1 lists the technology type. Column 2 lists the choices under that type. + |Type| Choice| |----| ------| |Operations support and security| Sysdig, StatusCake, Loki, Splunk, [Vault](https://www.vaultproject.io) @@ -34,6 +37,8 @@ Please note the following important considerations that can impact choices: ### Collaboration +Column 1 lists the technology type. Column 2 lists the choices under that type. + |Type| Choice| |----| ------| |Collaboration tools| [JIRA](https://www.atlassian.com/software/jira), [GitHub Discussions](https://github.com/features/discussions), [GitHub Issues](https://github.com/features/issues), [MS Teams](https://www.microsoft.com/en-ca/microsoft-teams/group-chat-software), [Loop](https://www.microsoft.com/en-us/microsoft-365/loop) @@ -41,10 +46,13 @@ Please note the following important considerations that can impact choices: ### Integration and data +Column 1 lists the technology type. Column 2 lists the choices under that type. + |Type| Choice| |----| ------| |API and data services| [API Gateway](https://digital.gov.bc.ca/bcgov-common-components/api-program-services/), [BC Data Catalogue](https://catalogue.data.gov.bc.ca) |Middleware and databases| PostgreSQL, MySQL, MongoDB, Kafka, Redis, NATS + ## Application hosting services options Each service offers unique features and capabilities that creates a secure and compliant environment for digital service hosting. Only services supported by Connected Services B.C. **(CSBC)** are listed: @@ -57,7 +65,7 @@ Each service offers unique features and capabilities that creates a secure and c - **Software as a Service (SaaS)**: offers ready-to-use software applications, hosted and managed by third-party providers. -Technical teams can use the table below compares the three to help choose the best hosting platform for their product. +Technical teams can use the table below for comparing Data centres, Private and Public cloud platforms. **Application hosting services comparison table** @@ -65,12 +73,12 @@ Column 1 lists features, column 2 has Data centre traditional hosting features, | | Data centre traditional hosting | [Private cloud OpenShift platform](docs/default/component/platform-developer-docs) | [Public cloud Azure and AWS Landing Zones](docs/default/component/public-cloud-techdocs) | |---|--------------------------------------|-----------------------------------|--------------------------------| -|Recommended for mission critical applications |Yes|Yes|No| -|Recommended technical skillset|
  • Server administration
  • Security operations
  • Technical architecture
  • Application development
  • Database administration |
  • DevOps
  • Full-stack development
  • Site reliability engineering
  • Security operations
  • Database administration |
  • DevOps
  • Full-stack development
  • Site reliability engineering
  • Security operations
  • Technical architecture
  • Network and infrastructure operations
  • Database administration | -|Hosting environment|Virtual machines and physical hardware| Containerized|Containerized and serverless| -|Highest [data classification](https://www2.gov.bc.ca/assets/gov/government/services-for-government-and-broader-public-sector/information-technology-services/standards-files/618_information_security_classification_standard.pdf) | Protected C|Protected B and C|Protected B| -| Procurement | [iStore order](https://ssbc-client.gov.bc.ca/order/istore.htm) | [Self-serve online](https://registry.developer.gov.bc.ca/login) | [Self-serve online](https://registry.developer.gov.bc.ca/login) | -| Elasticity and scalability |
  • Low
  • Resource must be pre-purchased |
  • Medium - High
  • Maximum allowed by project resource quota |
  • High
  • Scale as needed, limited only by product budget| -|Additional services|
  • Software Defined Network
  • S3 Object Store |
  • Software Defined Network
  • S3 Object Store
  • AI/ML
  • Security tools |
  • Checkpoint CSPM
  • All AWS IaaS/PaaS services available in Canada central region (ca-central-1) and United States east coast (us-east-1).
  • Does not include Marketplace services | -|Expertise available|
  • High
  • Extensive expertise within CSBC |
  • High
  • Extensive expertise within CSBC |
  • Medium
  • CSBC is developing expertise to support clients | -| Support assigned to product team| [Review shared responsibility model](https://digital.gov.bc.ca/technology/cloud/hosting-services/#shared) |[Review shared responsibility model](https://digital.gov.bc.ca/technology/cloud/hosting-services/#shared)|[Review shared responsibility model](https://digital.gov.bc.ca/technology/cloud/hosting-services/#shared)| +|Plaform recommended for mission critical applications? |Yes|Yes|No| +|The recommended technical skillsets|
  • Server administration
  • Security operations
  • Technical architecture
  • Application development
  • Database administration |
  • DevOps
  • Full-stack development
  • Site reliability engineering
  • Security operations
  • Database administration |
  • DevOps
  • Full-stack development
  • Site reliability engineering
  • Security operations
  • Technical architecture
  • Network and infrastructure operations
  • Database administration | +|The hosting environment|Virtual machines and physical hardware| Containerized|Containerized and serverless| +|The highest [data classification](https://www2.gov.bc.ca/assets/gov/government/services-for-government-and-broader-public-sector/information-technology-services/standards-files/618_information_security_classification_standard.pdf) | Protected C|Protected B and C|Protected B| +| The procurement process | [iStore order](https://ssbc-client.gov.bc.ca/order/istore.htm) | [Registry (a self-serve system](https://registry.developer.gov.bc.ca/login) | [Registry (a self-serve system)](https://registry.developer.gov.bc.ca/login) | +| The elasticity and scalability potential |
  • Low
  • Resource must be pre-purchased |
  • Medium - High
  • Maximum allowed by project resource quota |
  • High
  • Scale as needed, limited only by product budget| +|Additional services offered |
  • Software Defined Network
  • S3 Object Store |
  • Software Defined Network
  • S3 Object Store
  • AI/ML
  • Security tools |
  • Checkpoint CSPM
  • All AWS IaaS/PaaS services available in Canada central region (ca-central-1) and United States east coast (us-east-1).
  • Does not include Marketplace services | +|The expertise available|
  • High
  • Extensive expertise within CSBC |
  • High
  • Extensive expertise within CSBC |
  • Medium
  • CSBC is developing expertise to support clients | +| The support assigned to product team| [Review shared responsibility model](https://digital.gov.bc.ca/technology/cloud/hosting-services/#shared) |[Review shared responsibility model](https://digital.gov.bc.ca/technology/cloud/hosting-services/#shared)|[Review shared responsibility model](https://digital.gov.bc.ca/technology/cloud/hosting-services/#shared)| From 11899ff0627cd5a95cc6b662f8782161a499f141 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 15:57:22 -0800 Subject: [PATCH 13/52] Clarify column descriptions in comparison table --- docs/choosing-technology/how-to-select-technology.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/choosing-technology/how-to-select-technology.md b/docs/choosing-technology/how-to-select-technology.md index 4c04909..8845fe9 100644 --- a/docs/choosing-technology/how-to-select-technology.md +++ b/docs/choosing-technology/how-to-select-technology.md @@ -69,7 +69,7 @@ Technical teams can use the table below for comparing Data centres, Private and **Application hosting services comparison table** -Column 1 lists features, column 2 has Data centre traditional hosting features, column 3 has Private cloud OpenShift platform features, and column 4 has Public cloud Azure and AWS Landing Zones features. +Column 1 lists features, column 2 lists Data centre traditional hosting features, column 3 lists Private cloud OpenShift platform features, and column 4 lists Public cloud Azure and AWS Landing Zones features. | | Data centre traditional hosting | [Private cloud OpenShift platform](docs/default/component/platform-developer-docs) | [Public cloud Azure and AWS Landing Zones](docs/default/component/public-cloud-techdocs) | |---|--------------------------------------|-----------------------------------|--------------------------------| From 1b6c5a3fb643f8c3d3fb81f394aa8b843e095212 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 16:37:43 -0800 Subject: [PATCH 14/52] Revise documentation for B.C. Government GitHub usage Updated text for clarity and consistency, including links to support resources and security guidance. Adjusted formatting and corrected typographical errors. --- .../bc-government-organizations-in-github.md | 63 ++++++++++--------- 1 file changed, 33 insertions(+), 30 deletions(-) diff --git a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md index 7f18640..d9c7848 100644 --- a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md +++ b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md @@ -1,53 +1,56 @@ # B.C. Government organizations in GitHub -The [Digital Principles for B.C. Government](https://www2.gov.bc.ca/gov/content/governments/policies-for-government/core-policy/policies/im-it-management#12.1.1.5) supports and encourages product teams to work in the open. GitHub **(GH)** is the leading platform for open-source projects and collaboration. +The [Digital Principles for B.C. Government](https://www2.gov.bc.ca/gov/content/governments/policies-for-government/core-policy/policies/im-it-management#12.1.1.5) supports and encourages product teams to work in the open. GitHub is the leading platform for open-source projects and collaboration. With GiHub Enterprise Cloud, we can: - - Collaborate with the open-source community to build software - - Support innvation - - Share code and best practices - - Track issues and feature requests - - Use tools for team and project management - - Save costs and time + - Collaborate with the open-source community to build software + - Support innvation + - Share code and best practices + - Track issues and feature requests + - Use tools for team and project management + - Save costs and time -The **Developer Experience team** manages B.C. Government's GitHub environments. For questions, concerns, or feedback, please [submit a support request on JSM]( https://citz-do.atlassian.net/servicedesk/customer/portal/2). +The **Developer Experience team** manages B.C. Government's GitHub environments. For questions, concerns, or feedback, please [submit a support request on our Jira Service Manager system]( https://citz-do.atlassian.net/servicedesk/customer/portal/2). For users who need quick access to common topics related to using GitHub in B.C. Government, please see the [GitHub for B.C. Government quick reference guide](docs/sample-govorginGH-quickref.md) instead of this doc. ## Organizations in GitHub -We have two GitHub organizations **(org)**: `bcgov` and `bcgov-c`: +We have two GitHub organizations, commony shortened to **"org"**: `bcgov` and `bcgov-c`: + ```mermaid graph TD; + accTitle: mermaid flowchart of GitHub orgs + accDescr: First tier is Enterprise GitHub Cloud and second tier is bcgov and bcgov-c A[GitHub Enterprise Cloud] --> B[bcgov]; A --> C[bcgov-c]; ``` -On July 2024, we enabled Single-Sign on **(SSO)** for `bcgov`. For `bcgov-c`, we enabled SSO on August 2024. All members must be authenticated with IDIRs, including contractors. Our [Single Sign-On (SSO) doc](#single-sign-on) has more information about the transition. +On July 2024, we enabled Single-Sign On **(SSO)** for `bcgov`. We enabled SSO for `bcgov-c` on August 2024. All members must be authenticated with IDIRs, including contractors. The [GitHub Single Sign-On (SSO) section](#single-sign-on) has more information about the transition. -To link GH accounts and IDIRs, [follow the SSO enablement instructions](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/bc-government-organizations-in-github/#directions-to-sign-up-and-link-your-account-for-bcgov). +To link GH accounts and IDIRs, [follow our SSO enablement instructions](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/bc-government-organizations-in-github/#directions-to-sign-up-and-link-your-account-for-bcgov). ### `bcgov` -The `bcgov` org hosts public repositories **(repos)** and has over 1000 repos. Each repo holds open-source code, public documents, and inner-source contribution models developed by B.C. government teams. +The `bcgov` org hosts public repositories, often shortened to **(repos)**. There's over 1000 repos. Each repo holds open-source code, public documents, and inner-source contribution models developed by B.C. Government teams. -All content in this org must be public to align with [B.C. Government's Digital Principles](https://digital.gov.bc.ca/policies-standards/dcop/). Anyone with membership can create repos. +All content hosted on this org must be public to align with [B.C. Government's Digital Principles](https://digital.gov.bc.ca/policies-standards/dcop/). Anyone with membership can create repos. ### `bcgov-c` We use `bcgov-c` for **private** repos with confidential code and documents. If a team needs a location for private code, or is working to make code public, this is the right org. -Only the Developer Experience team can create repos in `bcgov-c`. To request a repo, please [submit a support request on JSM](https://citz-do.atlassian.net/servicedesk/customer/portal/2/group/9/create/60). +Only the Developer Experience team can create repos in `bcgov-c`. To request a repo, please [submit a support request on our Jira Service Manager system](https://citz-do.atlassian.net/servicedesk/customer/portal/2/group/9/create/60). ### Security features for both organizations -Please keep in mind that application and code security are complex. The [Security and Privacy Guidance](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/security/security-and-privacy-compliance-and-guidance/) and [Security best practices for apps](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/security/best-practices-for-apps/) docs offers more comprehensive guidance. +Please keep in mind that application and code security are complex. The [Security and Privacy Guidance doc](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/security/security-and-privacy-compliance-and-guidance/) and [Security best practices for apps doc](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/security/best-practices-for-apps/) offer more comprehensive guidance. Both orgs come with various security features to protect repos and its code. We've highlighted some prominent features and best practices below. #### Costs -**`bcgov`:** no cost for security features because GH gives them free to public repos. +**`bcgov`:** no cost for security features because GH gives them free to public repos. **`bcgov-c`**: cost for security features because GH charges a fee for private repos. **But** the Developer Experience team covers cost **without cost recovery**. @@ -61,18 +64,18 @@ Both orgs come with various security features to protect repos and its code. We' #### Best practices -* **Keep features enabled in repos**. Even if some can be reconfigured at the repo level, they're there the team secure code. +* **Keep features enabled in repos**. Even if some can be reconfigured at the repo level, they keep the team secure code. -* **Use the GH [Security Overview page](https://github.com/orgs/bcgov/security/overview)** to check any detected issues for repos, especially if working on multiple repos. +* **Use the [GitHub Security Overview page](https://github.com/orgs/bcgov/security/overview)** to check any detected issues for repos, especially if working on multiple repos. * **Take action on any issue surfaced by security features immediately**. Quick action-even if false positives-can stop big problems or becoming "noise" to ignore. ## Single Sign-On -Because IDIRs are mandatory for both organizations, we have created an [IDIR guide](github-transition-guide.md). We've also included contractor-specific instructions. Please note that IDIR order completion can take **several** days. +Because IDIRs are mandatory for both organizations, we have created [an IDIR guide for SSO](github-transition-guide.md). We've also included contractor-specific instructions. Please note that IDIR order completion can take **several** days. -If the instructions and troubleshooting help below doesn't resolve any issues, please [submit a support request on JSM]( https://citz-do.atlassian.net/servicedesk/customer/portal/2). +If the instructions and troubleshooting help below doesn't resolve any issues, please [submit a support request on our Jira Service Manager system]( https://citz-do.atlassian.net/servicedesk/customer/portal/2). ### Security Insights for GitHub Enterprise-linked organizations @@ -86,8 +89,8 @@ Branch protection allows specified members to push to the protected branch. The 2. Log into GitHub with your personal login. 3. [Authenticate your IDIR](https://github.com/orgs/bcgov/sso) 4. You'll get an email with an invitation to join the `bcgov` GitHub organization. The invitation will be sent to the email address associated with your GitHub account. - a. Refer to the [troubleshooting](#troubleshooting) section if you didn't receive an email. -5. Your teammates can add you to your team's repositories. We recommend teams use [GitHub teams](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. + a. Refer to the [SSO troubleshooting section](#troubleshooting) if you didn't receive an email. +5. Your teammates can add you to your team's repositories. We recommend teams use the [GitHub teams page](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. 6. [Authorize your personal access tokens and/or SSH keys](github-transition-guide.md#resetting-github-keys). That’s it, both accounts are now joined. @@ -100,8 +103,8 @@ A similar process applies for `bcgov-c`. 1. Log into GitHub with your personal login. 1. [Authenticate your IDIR](https://github.com/orgs/bcgov-c/sso) 1. You'll get an email with an invitation to join the `bcgov-c` GitHub organization. The invitation will be sent to the email address associated with your GitHub account. - 1. Refer to the [troubleshooting](#troubleshooting) section if you didn't receive an email. -1. Your teammates can add you to your team's repositories. We recommend teams use [GitHub teams](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. + 1. Refer to the [SSO troubleshooting section](#troubleshooting) if you didn't receive an email. +1. Your teammates can add you to your team's repositories. We recommend teams use [GitHub teams page](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. 1. [Re-authorize your personal access tokens and/or SSH keys](github-transition-guide.md#resetting-github-keys). That’s it, both accounts are now joined. @@ -122,11 +125,11 @@ That’s it, both accounts are now joined. If you didn't get an email invitation to join either organizations, you can check your organization status and invites: -1. Go to [https://github.com](https://github.com) -1. Sign in with the account used to join the [`bcgov`](#directions-to-sign-up-and-link-your-account-for-bcgov) or [`bcgov-c`](#directions-to-sign-up-and-link-your-account-for-bcgov-c) organization -1. Click on your profile picture -1. Choose the "Your organizations" option from the menu -1. Confirm the `bcgov` and/or `bcgov-c` organization is listed under the "Organizations" page -1. Click the "Accept" button next to the organization +1. Go to [https://github.com](https://github.com). +1. Sign in with the account used to join the [`bcgov` org](#directions-to-sign-up-and-link-your-account-for-bcgov) or [`bcgov-c` org](#directions-to-sign-up-and-link-your-account-for-bcgov-c). +1. Click on your profile picture. +1. Choose the "Your organizations" option from the menu. +1. Confirm the `bcgov` and/or `bcgov-c` organization is listed under the "Organizations" page. +1. Click the "Accept" button next to the organization. ![Screenshot of a user's organizations. The screen displays the `bcgov-c` organization with "Member" beside it. Next to it is "Invitation expires in 7 days" with Accept and Decline buttons.](../images/invitation.png) From c80af9b56f82c3477a2dfea0d1f60f9ad253ac33 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 16:41:34 -0800 Subject: [PATCH 15/52] Clarify privacy and copyright requirements in documentation Updated formatting and clarified terms related to personal information, copyright, and content ownership. --- .../evaluate-open-source-content.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/docs/use-github-in-bcgov/evaluate-open-source-content.md b/docs/use-github-in-bcgov/evaluate-open-source-content.md index b3d693a..5288a43 100644 --- a/docs/use-github-in-bcgov/evaluate-open-source-content.md +++ b/docs/use-github-in-bcgov/evaluate-open-source-content.md @@ -16,9 +16,7 @@ The [First steps working in GitHub doc](https://developer.gov.bc.ca/docs/default ## Privacy -Personal information **(PI)**, like name, phone number, photo, address, driver's license numbers, etc., must not be posted in public repos. - -Teams should contact their privacy analyst for help in privacy assessments. +Personal information **(P.I.)**, like name, phone number, photo, address, driver's license numbers, etc., must not be posted in public repos. Teams should contact their privacy analyst for help in privacy assessments. ## Security @@ -28,11 +26,11 @@ Anything labelled **'public'** must meet the [Information Security Classificatio ## Copyright -The requirements below are mandatory before posting on GH: +The requirements below are mandatory before posting on GitHub: -* Content is created only by B.C. government employees +* Content is created only by B.C. Government employees -* Content is owned by the B.C. government and doesn't have third-party content. Collect copies of contracts related to the content for review with the [Intellectual Property Program](https://www2.gov.bc.ca/gov/content/governments/services-for-government/policies-procedures/intellectual-property/intellectual-property-program) **(IPP)**. +* Content is owned by the B.C. Government and doesn't have third-party content. Collect copies of contracts related to the content for review with the [Intellectual Property Program](https://www2.gov.bc.ca/gov/content/governments/services-for-government/policies-procedures/intellectual-property/intellectual-property-program) **(IPP)**. * Content doesn't have terms of use or exclusive licences that prohibit the Province from licensing the content on GitHub. Collect information about any terms of use or licences related to the content for review with the IPP. From 571167890b63371380bd4314c2f2c60b62f677af Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 16:52:16 -0800 Subject: [PATCH 16/52] Clarify SSO terminology and improve document grammar Updated terminology for clarity and consistency regarding Single Sign-On (SSO) and Jira Service Manager system. Made minor grammatical corrections throughout the document. --- .../github-transition-guide.md | 32 +++++++++---------- 1 file changed, 15 insertions(+), 17 deletions(-) diff --git a/docs/use-github-in-bcgov/github-transition-guide.md b/docs/use-github-in-bcgov/github-transition-guide.md index 0fcc9c5..6726584 100644 --- a/docs/use-github-in-bcgov/github-transition-guide.md +++ b/docs/use-github-in-bcgov/github-transition-guide.md @@ -1,16 +1,14 @@ -# Transition Guides for GitHub SSO +# Transition Guides for GitHub Single Sign-On -The [B.C. Government organizations in GitHub doc](bc-government-organizations-in-github.md#single-sign-on) has an overview of SSO. Please read that section before reading these transition guides because the guides are supplementary material. +The [B.C. Government organizations in GitHub doc](bc-government-organizations-in-github.md#single-sign-on) has an overview of Single Sign-On (SSO). Please read that section before reading these transition guides because the guides are supplementary material. The transition guide doc hosts two guides: -- [**IDIR Guide**](#idir-guide): more detailed information about IDIRs and how they relate to the mandatory SSO feature on `bcgov` and `bcgov`. +- [**IDIR Guide**](#idir-guide): has more detailed information about IDIRs and how they relate to the mandatory SSO feature on `bcgov` and `bcgov`. - [**Technical Guide**](#technical-guide): helps GitHub users prepare for the SSO feature, and confirms if users completed joining successfully - If there’s a topic isn’t covered in the guide, please [submit a support request on JSM](https://citz-do.atlassian.net/servicedesk/customer/portal/2). - - + If there’s a topic isn’t covered in the guide, please [submit a support request on our Jira Service Manager system](https://citz-do.atlassian.net/servicedesk/customer/portal/2). ## IDIR Guide @@ -33,11 +31,11 @@ B.C. Government employees have the default configuration compatible with SSO. Th ### Compatible IDIRs for contractors If a user is a contracted worker, the process may be more complex depending on IDIR types. The table below gives an overview between P2 and E5 IDIRs. -We don’t foresee any technical issues with SSO if contractors have either IDIR type. If this isn’t the case, please [submit a support request on JSM](https://citz-do.atlassian.net/servicedesk/customer/portal/2). +We don’t expect any technical issues with SSO if contractors have either IDIR type. If this isn’t the case, please [submit a support request on our Jira Service Manager system](https://citz-do.atlassian.net/servicedesk/customer/portal/2). #### P2 and E5 IDIR comparison table -Column 1 lists IDIR features, column 2 has P2 features, and column 3 has E5 features. +Column 1 lists IDIR features, column 2 lists P2 features, and column 3 lists E5 features. | | P2 IDIR | E5 IDIR | @@ -49,7 +47,7 @@ Column 1 lists IDIR features, column 2 has P2 features, and column 3 has E5 feat Please see [Service Bulletin 1350](https://ociomysc.service-now.com/sp?id=kb_article&sys_id=7a69f65fdbff9d10fa86193813961978&spa=1) for more information. -It’s very likely contractors already with IDIRs have P2. If linking doesn't work, please call 7-7000 or open a ticket to confirm through [MyService Centre](https://ociomysc.service-now.com/sp?id=ocio_sr_incident_management). +It’s very likely contractors already with IDIRs have P2. If linking doesn't work, please call 7-7000 or [open a ticket to confirm on MyService Centre](https://ociomysc.service-now.com/sp?id=ocio_sr_incident_management). #### IDIR expiry @@ -63,18 +61,18 @@ Each ministry has an authorized user who submits orders in [MyService Centre](ht ## Multiple IDIRs -Developers with multiple IDIRs can join their most permanent IDIR to their GitHub ID. They can change IDIRs at any time. We tested and can confirm that users make changes on their own. +Developers with multiple IDIRs can join their most permanent IDIR to their GitHub ID. They can change IDIRs at any time. We tested and can confirm that users can make changes on their own. The important things to keep in mind are: - The IDIR must not be expired - Our team cannot manage IDIR expiry dates -If you don’t see information that could be helpful on this guide, please let us know through [submit a support request on JSM](https://citz-do.atlassian.net/servicedesk/customer/portal/2). +If you don’t see information that could be helpful on this guide, please let us know through [submit a support request on our Jira Service Manager system](https://citz-do.atlassian.net/servicedesk/customer/portal/2). #### P2 IDIR login -Vendors using both **P2 IDIRs** and external emails (e.g. ggg123@gmail.com) must log in with **\@gov.bc.ca**. +Vendors using both **P2 IDIRs** and external emails (e.g. ggg123@gmail.com) must log in with **@gov.bc.ca**. ## Technical Guide @@ -94,7 +92,7 @@ GitHub doesn't offer users a screen to confirm authentication. There are 2 alter > 2. Go to your profile by clicking your avatar on the top right. > 3. Click "Settings". > 4. Click "[Sessions](https://github.com/settings/sessions)". -> 5. Click "See more" button for the current web session +> 5. Click "See more" button for the current web session. > 6. If you're authenticated, GitHub will show details of your current session, inclusive of your device, your last login location, and when you last signed in. Clicking on the three dots by the "Your session expires" section will display the NameID from the linked IDIR. We've included a screenshot as an example: @@ -102,11 +100,11 @@ GitHub doesn't offer users a screen to confirm authentication. There are 2 alter ### Outside Collaborators -We discontinued the option to add [outside collaborators](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/adding-outside-collaborators-to-repositories-in-your-organization). GitHub will send invitations to current outside collaborators to become full members on `bcgov`, and IDIRs are needed. +We discontinued the option to add outside collaborators. GitHub explains [more about outside collaborators on their doc](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/adding-outside-collaborators-to-repositories-in-your-organization). GitHub will send invitations to current outside collaborators to become full members on `bcgov`, and IDIRs are needed. -To create IDIRs or have more information, please read [the IDIR guide](#idir-transition-guide). +To create IDIRs or have more information, please read [the IDIR guide section](#idir-transition-guide) of this doc -Accessess will stay the same. +All accesses will stay the same. ### No new GitHub ID needed @@ -114,7 +112,7 @@ GitHub differs from other tools that use IDIR as the user account to access serv The reason is due to GitHub’s open source code community ecosystem. A part of our commitment to open government is the `bcgov` GitHub org. We set up GitHub accounts to be associated with many different repos and orgs because throughout their careers, developers contribute to many different open projects and organizations. -With the GitHub SSO upgrade, contractors and developers working in the `bcgov` GitHub org will continue to use their GitHub to login to access GitHub. The extra step is the prompt to login to IDIR to comply with security policies. +With the GitHub SSO upgrade, contractors and developers working in the `bcgov` GitHub org will continue to use their GitHub to login to access GitHub. The extra step is the prompt to login to IDIR so we comply with security policies. ### Resetting GitHub Keys From d15e6322e80c6f99bc8d99ecdee040c5a9f344b2 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 16:55:13 -0800 Subject: [PATCH 17/52] Fix spelling and capitalization in licensing document Corrected spelling and capitalization errors in the licensing guidelines. --- docs/use-github-in-bcgov/license-your-github-repository.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/use-github-in-bcgov/license-your-github-repository.md b/docs/use-github-in-bcgov/license-your-github-repository.md index 8e3fb3c..c03861f 100644 --- a/docs/use-github-in-bcgov/license-your-github-repository.md +++ b/docs/use-github-in-bcgov/license-your-github-repository.md @@ -2,16 +2,15 @@ Licences manage and share intellectual property for code and materials on GitHub. Any consumpation, shares, or contributions to a repo needs to be matched with the relevant licence. - -The Intellectual Property Program **(IPP)** must approve licences of B.C. government owned intellectual property. The only **exception** is if a ministry has either specific legislative authority or Treasury Board approval that lets them license the intellectual property rights of the Province to third parties. +The Intellectual Property Program **(IPP)** must approve licences of B.C. Government owned intellectual property. The only **exception** is if a ministry has either specific legislative authority or Treasury Board approval that lets them license the intellectual property rights of the Province to third parties. When IPP is the authority for the licensing, teams must work with IPP to find the best fit to meet the licensing needs of the project. IPP examines the development history of the content, somtetimes in the form of a conversation. Initial questions include the following: -- Is the content created solely by B.C. government employees? +- Is the content created solely by B.C. Government employees? -- Does the content contain only content owned by the B.C. government? Have you made sure that it doesn't contain any third-party content? +- Does the content contain only content owned by the B.C. Government? Have you made sure that it doesn't contain any third-party content? - Can you confirm that there are no terms of use or exclusive licensing arrangements that prohibit the Province from posting and licensing the content on GitHub? ## Guidance for choosing a licence From 2190863a52af5ca70d4ed62562235330fa5fd2f8 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 16:58:20 -0800 Subject: [PATCH 18/52] Fix typos and improve clarity in access removal guide --- .../remove-user-bcgov-github-access.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md b/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md index dc051f6..974f4ba 100644 --- a/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md +++ b/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md @@ -10,13 +10,13 @@ We have two steps to remove access: ## Step 1: Remove access to team repos -A GH user can access a team repo via GitHub team membership, or direct repo access. The GitHub help pages below offers guidance on how to complete removal: +A GitHub user can access a team repo via GitHub team membership, or direct repo access. The GitHub help pages below offers guidance on how to complete removal: -* [removing members from GitHub team(s)](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person) -* [removing members from repo "Collaborators & teams" setting](https://docs.github.com/en/organizations/organizing-members-into-teams/removing-organization-members-from-a-team) +1. [removing members from GitHub team(s)](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person) +2. [removing members from repo "Collaborators & teams" setting](https://docs.github.com/en/organizations/organizing-members-into-teams/removing-organization-members-from-a-team) ## Step 2: Remove membership in `bcgov` and/or `bcgov-c` orgs -The Developer Experience team doesn't remove membership from the `bcgov` and `bcgov-c` orgs. Membership is controlled by IDIRs, so a team's manager must [cancel a user's IDIR account on MySC](https://ociomysc.service-now.com/sp?id=kb_article&sys_id=5f3fab83db1a5690fa86193813961933). This makes sure users are removed, however, cancellation may take a few days. +The Developer Experience team doesn't remove membership from the `bcgov` and `bcgov-c` orgs. Membership is controlled by IDIRs, so a team's manager must [cancel a user's IDIR account on MyService Centre](https://ociomysc.service-now.com/sp?id=kb_article&sys_id=5f3fab83db1a5690fa86193813961933). This makes sure users are removed, however, cancellation may take a few days. Please remove the member's access from team repos immediately. From 625d907c8476519f68fd0525b9c9d588d0cead69 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 16:59:50 -0800 Subject: [PATCH 19/52] Update required-pages-for-github-repository.md --- .../required-pages-for-github-repository.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/use-github-in-bcgov/required-pages-for-github-repository.md b/docs/use-github-in-bcgov/required-pages-for-github-repository.md index 198586e..252e39f 100644 --- a/docs/use-github-in-bcgov/required-pages-for-github-repository.md +++ b/docs/use-github-in-bcgov/required-pages-for-github-repository.md @@ -13,15 +13,15 @@ All repos need a license. Choose the best fit for the team repo. Important infor ## README file -Please read and adapt the [GH README guidelines](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes) and [5 tips for making your GitHub profile page accessible](https://github.blog/developer-skills/github/5-tips-for-making-your-github-profile-page-accessible/) for guidance to create good README files. Teams can find extensive documentation on GH about README files for repos. +Please read and adapt the [GitHub README guidelines](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes) and [5 tips for making your GitHub profile page accessible](https://github.blog/developer-skills/github/5-tips-for-making-your-github-profile-page-accessible/) for guidance to create good README files. Teams can find extensive documentation on GH about README files for repos. -Aside from GH documentation, please include: +Aside from GitHub documentation, please include: * A brief project description. * An overview of how to contribute to the team repo, and a link to repo contribution guidelines. -* Dependent on licence, boilerplate text. [Licenses for GitHub repos doc](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/license-your-github-repository/) offers more information about the topic. +* Dependent on licence, boilerplate text. The [Licenses for GitHub repos doc](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/license-your-github-repository/) offers more information about the topic. * A link to team Code of Conduct file. From 6ad40b4536ff81e6e6085777a1badf80c7657307 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 17:01:41 -0800 Subject: [PATCH 20/52] Fix capitalization and formatting in documentation --- .../start-working-in-bcgov-github-organization.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/use-github-in-bcgov/start-working-in-bcgov-github-organization.md b/docs/use-github-in-bcgov/start-working-in-bcgov-github-organization.md index 373deff..e336ea8 100644 --- a/docs/use-github-in-bcgov/start-working-in-bcgov-github-organization.md +++ b/docs/use-github-in-bcgov/start-working-in-bcgov-github-organization.md @@ -29,7 +29,7 @@ Both methods use similar ways to release the code. They differ in project manage * Confirming team authority to license. * Choosing an open-source license, and consult with the Intellectual Property Program **(IPP)** to make sure government has the right to release the code. - * If using code from another open-source project, follow to the existing licensing provisions, and make sure the licences are compatiable. Per the [evaluate open-source content doc](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/evaluate-open-source-content/), don't infringe on intellectual property rights. These can include, patent rights, trademarks in the code or documentation. + * If using code from another open-source project, follow to the existing licensing provisions, and make sure the licences are compatiable. Per [the evaluate open-source content doc](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/evaluate-open-source-content/), don't infringe on intellectual property rights. These can include, patent rights, trademarks in the code or documentation. * Confirming that there are no restrictions on releasing the code or documentation imposed by legislation, policy or contracts. @@ -70,4 +70,4 @@ Sometimes, it's useful and appropriate for employees to contribute to non-B.C. G * Confirm team authority to license. -Employees can also contribute to non-B.C. government owned intellectual property rights outside their professional roles by using their personal email linked to their GitHub account. +Employees can also contribute to non-B.C. Government owned intellectual property rights outside their professional roles by using their personal email linked to their GitHub account. From 74afc126b8085352e1a6d6c9a9b71186bad54ec4 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 17:03:55 -0800 Subject: [PATCH 21/52] Delete docs/welcome-to-bc-gov.md --- docs/welcome-to-bc-gov.md | 45 --------------------------------------- 1 file changed, 45 deletions(-) delete mode 100644 docs/welcome-to-bc-gov.md diff --git a/docs/welcome-to-bc-gov.md b/docs/welcome-to-bc-gov.md deleted file mode 100644 index 8bbba17..0000000 --- a/docs/welcome-to-bc-gov.md +++ /dev/null @@ -1,45 +0,0 @@ -# Welcome to the B.C. government - -There are a plethora of things to consider when developing apps for [core government](https://www2.gov.bc.ca/gov/content/governments/organizational-structure/ministries-organizations/ministries). This list will hopefully get you started on the right foot. - -## Five quick things to get you started - -1. Bookmark this site! It serves as the central hub for all development-related matters - -2. Get [access to the BCGov GitHub organization](../use-github-in-bcgov/bc-government-organizations-in-github/#bcgov). This is the default place for code to be stored in the BC Gov. Learn more about [the different B.C. Government GitHub organizations](../use-github-in-bcgov/bc-government-organizations-in-github/#organizations-in-github). - -3. [Get access to Rocket.Chat](../rocketchat/steps-to-join-rocketchat) and BC Government [GitHub Discussions](https://github.com/bcgov/bcgov-community-discussions). These are where the developer community gathers to ask questions, support each other with issues and is often the best source of support for internal services such as our cloud services and common components. - -4. [Explore the internal services](https://digital.gov.bc.ca/common-components/) and [Saas Tools](https://digital.gov.bc.ca/cloud/services/saas/) you can re-use to supports your work. - -5. Learn about what's happening in the [BC Gov Digital Ecosystem](https://digital.gov.bc.ca/blog/) - -Beyond this, most things are up to your team to decide, and not standardized. Browse the [documentation](/docs/) on this site to understand some of the existing resources available to you. Your team may have more guidance specific to your Ministry and team processes. - -## Where things are hosted - -### Working in the Private Cloud a.k.a. Open Shift - -* [Open Shift Intro](https://digital.gov.bc.ca/cloud/services/private/intro/) -* [Account access](/docs/default/component/platform-developer-docs/docs/openshift-projects-and-access/grant-user-access-openshift/) -* [Training](/docs/default/component/platform-developer-docs/docs/training-and-learning/training-from-the-platform-services-team/) - -### Working in the Public Cloud - -* [Public Cloud Intro](https://digital.gov.bc.ca/cloud/services/public/intro/) -* [Account access](/docs/default/component/public-cloud-techdocs/provision-a-project-set/#account-access) -* [Training](/docs/default/component/platform-developer-docs/#training-and-learning) - -### On Premise Hosting - -* [Hosting Services Intro](https://www2.gov.bc.ca/gov/content/bc-procurement-resources/buy-for-government/goods-and-services-catalogue/hosting-services) - -## Security and compliance guidance and policies - -You don't need to memorize these, but having them as context is helpful for navigating the compliance and governance environment you're working within. - -* [Privacy and personal information in the B.C. public sector](https://www2.gov.bc.ca/gov/content/governments/services-for-government/information-management-technology/privacy) -* [FOIPPA Quick Reference](https://raw.githubusercontent.com/bcgov/devhub-resources/master/resources/privacy/foippa_quick_reference.pdf) -* [B.C. government OpenShift DevOps security considerations](https://developer.gov.bc.ca/docs/default/component/platform-developer-docs/docs/security-and-privacy-compliance/platform-security-compliance/) -* [BC Gov Policy for GitHub](https://github.com/bcgov/BC-Policy-Framework-For-GitHub/blob/master/README.md) -* [IMIT standards](https://www2.gov.bc.ca/gov/content/governments/services-for-government/policies-procedures/im-it-standards) From 953582c9cae7ae20e04c48b45d7d78bd6e5db244 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 17:04:26 -0800 Subject: [PATCH 22/52] Delete docs/security-and-privacy-compliance-and-guidance.md --- docs/security-and-privacy-compliance-and-guidance.md | 1 - 1 file changed, 1 deletion(-) delete mode 100644 docs/security-and-privacy-compliance-and-guidance.md diff --git a/docs/security-and-privacy-compliance-and-guidance.md b/docs/security-and-privacy-compliance-and-guidance.md deleted file mode 100644 index 8b13789..0000000 --- a/docs/security-and-privacy-compliance-and-guidance.md +++ /dev/null @@ -1 +0,0 @@ - From cf5118dc8ab05979be7abb1373f096285d30e2f5 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 17:05:24 -0800 Subject: [PATCH 23/52] Fix typo in working-with-data.md --- docs/working-with-data.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/working-with-data.md b/docs/working-with-data.md index 4c87269..cc72956 100644 --- a/docs/working-with-data.md +++ b/docs/working-with-data.md @@ -39,5 +39,5 @@ The province's area, varied topography and predominantly natural resource based ## Support -If you're working on a project that will hold citizen or buisness data, or needs to connect to an existing resource, the [Data Services Client Hub](https://dpdd.atlassian.net/servicedesk/customer/portal/1) can help connect you to the right place for support. +If you're working on a project that will hold citizen or business data, or needs to connect to an existing resource, the [Data Services Client Hub](https://dpdd.atlassian.net/servicedesk/customer/portal/1) can help connect you to the right place for support. From 6060d592a9bbb2d4ca23d30dc7b1d95d063a4bf0 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 17:09:59 -0800 Subject: [PATCH 24/52] Revise title to 'bcgov, bcgov-c, and SSO' Updated the title of the document to reflect the specific organizations and clarified the context for GitHub usage in B.C. Government. --- .../bc-government-organizations-in-github.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md index d9c7848..c117366 100644 --- a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md +++ b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md @@ -1,4 +1,4 @@ -# B.C. Government organizations in GitHub +# bcgov, bcgov-c, and SSO The [Digital Principles for B.C. Government](https://www2.gov.bc.ca/gov/content/governments/policies-for-government/core-policy/policies/im-it-management#12.1.1.5) supports and encourages product teams to work in the open. GitHub is the leading platform for open-source projects and collaboration. From ab7150895e5d88c3e49abcb090835379af2dcff7 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 17:14:54 -0800 Subject: [PATCH 25/52] Update title of transferring repos documentation --- docs/use-github-in-bcgov/transferring-repos-to-bc-gov-orgs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-github-in-bcgov/transferring-repos-to-bc-gov-orgs.md b/docs/use-github-in-bcgov/transferring-repos-to-bc-gov-orgs.md index ac202bc..b7f45d1 100644 --- a/docs/use-github-in-bcgov/transferring-repos-to-bc-gov-orgs.md +++ b/docs/use-github-in-bcgov/transferring-repos-to-bc-gov-orgs.md @@ -1,4 +1,4 @@ -# Transferring repositories +# Transferring repos to bcgov or bcgov-c This page explains the process to move repositories from a team or ministry's GitHub organization to either [bcgov](https://github.com/bcgov) or [bcgov-c](https://github.com/bcgov-c) GitHub organization. From 50799865ba1adef862a0f66e5fcddabd6ccd1228 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 17:16:31 -0800 Subject: [PATCH 26/52] Change title to IDIR and technical guide for SSO Updated the title of the transition guide to reflect IDIR and technical aspects of SSO. --- docs/use-github-in-bcgov/github-transition-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-github-in-bcgov/github-transition-guide.md b/docs/use-github-in-bcgov/github-transition-guide.md index 6726584..ed3b180 100644 --- a/docs/use-github-in-bcgov/github-transition-guide.md +++ b/docs/use-github-in-bcgov/github-transition-guide.md @@ -1,4 +1,4 @@ -# Transition Guides for GitHub Single Sign-On +# IDIR and technical guide for SSO The [B.C. Government organizations in GitHub doc](bc-government-organizations-in-github.md#single-sign-on) has an overview of Single Sign-On (SSO). Please read that section before reading these transition guides because the guides are supplementary material. From 2b8cbb42464afbc7fc734537ba310387ac33713b Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Fri, 16 Jan 2026 17:17:31 -0800 Subject: [PATCH 27/52] Update navigation structure in mkdocs.yml --- mkdocs.yml | 31 +++++++++++++++---------------- 1 file changed, 15 insertions(+), 16 deletions(-) diff --git a/mkdocs.yml b/mkdocs.yml index 9634a52..8086c22 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -20,40 +20,39 @@ exclude_docs: | supports_for_developers.md nav: - - Introduction: index.md + - Welcome to the B.C. Government: index.md # - Digital Government: digital_government.md # - Ways of Working: ways_of_working.md # - Supports for developers: supports_for_developers.md - - Welcome to the B.C. government: welcome-to-bc-gov.md - - Selecting Technology: choosing-technology/how-to-select-technology.md + - Choosing project technology: choosing-technology/how-to-select-technology.md - Security and Privacy: - - Security and Privacy Guidance: security/security-and-privacy-compliance-and-guidance.md + - Security and Privacy guidance: security/security-and-privacy-compliance-and-guidance.md - Security best practices for apps: security/best-practices-for-apps.md + - Accessibility: accessibility-resources.md + - The design system: design-system/about-the-design-system.md - GitHub in the B.C. government: - - BC Government organizations in GitHub: use-github-in-bcgov/bc-government-organizations-in-github.md - B.C. Government GitHub Quick Reference: use-github-in-bcgov/quick-reference.md - - Security Features for BC Government GitHub Users: use-github-in-bcgov/github-security.md - - Remove a user's BCGov GitHub access: use-github-in-bcgov/remove-user-bcgov-github-access.md - - GitHub SSO transition guide: use-github-in-bcgov/github-transition-guide.md + - bcgov, bcgov-c, and SSO: use-github-in-bcgov/bc-government-organizations-in-github.md + - SSO IDIR and technical guide: use-github-in-bcgov/github-transition-guide.md + - First steps working in GitHub: use-github-in-bcgov/start-working-in-bcgov-github-organization.md - Evaluate open-source content: use-github-in-bcgov/evaluate-open-source-content.md + - Licenses for GitHub repos: use-github-in-bcgov/license-your-github-repository.md - Required pages for a GitHub repository: use-github-in-bcgov/required-pages-for-github-repository.md - - Start working in the BCGov GitHub organization: use-github-in-bcgov/start-working-in-bcgov-github-organization.md - - License your GitHub repository: use-github-in-bcgov/license-your-github-repository.md - - Transfer a repository to a BC Government GitHub Organization: use-github-in-bcgov/transferring-repos-to-bc-gov-orgs.md + - Transferring repos to bcgov or bcgov-c: use-github-in-bcgov/transferring-repos-to-bc-gov-orgs.md + - Removing member access: use-github-in-bcgov/remove-user-bcgov-github-access.md + - Rocket.Chat: - Join the B.C. Government Rocket.Chat: rocketchat/steps-to-join-rocketchat.md - Rocket.Chat etiquette: rocketchat/rocketchat-etiquette.md - Rocket.Chat channel descriptions: rocketchat/rocketchat-channel-descriptions.md - - Developing better questions: rocketchat/get-help-in-rocketchat.md - - Accessibility: accessibility-resources.md - - Design System: - - About the Design System: design-system/about-the-design-system.md + - Developing better questions: rocketchat/get-help-in-rocketchat.md + - Quickstart Wizards: - Quickstart for OpenShift Wizard: wizards/quickstart-for-openshift-wizard.md - DevHub Content Partner Guide: content-partner-guide.md - DevHub Content Syntax Guide: content-syntax-guide.md - Working with data: working-with-data.md - - BC Government API Guidelines: bc-government-api-guidelines.md + - BC Government API Guidelines: bc-government-api-guidelines.md # - Developer community: developer_community.md # - Application lifecycle: application_lifecycle.md From fe968b473a885e10665c1d94988f07d6c35f5269 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 08:23:49 -0800 Subject: [PATCH 28/52] Update docs/choosing-technology/how-to-select-technology.md Co-authored-by: Monica Granbois --- docs/choosing-technology/how-to-select-technology.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/choosing-technology/how-to-select-technology.md b/docs/choosing-technology/how-to-select-technology.md index 8845fe9..ae78ae1 100644 --- a/docs/choosing-technology/how-to-select-technology.md +++ b/docs/choosing-technology/how-to-select-technology.md @@ -7,7 +7,7 @@ We offer many options within B.C. Government systems. The tables below show a cr ## Current technology options -Although there's numerous choices, the options in the table below isn't exhaustive, nor represents an endorsement of any particular choice. Every team should do its own research before deciding which technology best suits their needs and context. +Although there's numerous choices, the options in the table below aren't exhaustive, nor represents an endorsement of any particular choice. Every team should do its own research before deciding which technology best suits their needs and context. Please note the following important considerations: From baaa12fdf8e03ced479c7a46bacb3b00b6c13a98 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 08:24:23 -0800 Subject: [PATCH 29/52] Update docs/choosing-technology/how-to-select-technology.md Co-authored-by: Monica Granbois --- docs/choosing-technology/how-to-select-technology.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/choosing-technology/how-to-select-technology.md b/docs/choosing-technology/how-to-select-technology.md index ae78ae1..8cd1675 100644 --- a/docs/choosing-technology/how-to-select-technology.md +++ b/docs/choosing-technology/how-to-select-technology.md @@ -32,7 +32,7 @@ Column 1 lists the technology type. Column 2 lists the choices under that type. |Type| Choice| |----| ------| -|Operations support and security| Sysdig, StatusCake, Loki, Splunk, [Vault](https://www.vaultproject.io) +|Operations support and security| [Sysdig](/docs/default/component/platform-developer-docs/docs/app-monitoring/sysdig-monitor-setup-team/), StatusCake, [Loki](/docs/default/component/platform-developer-docs/docs/app-monitoring/best-practices-for-application-logging-in-openshift/#console-logs-in-loki), Splunk, [Vault](/docs/default/component/platform-developer-docs/docs/secrets-management/vault-getting-started-guide/) |Application hosting| [Learn about application hosting options](#application-hosting-services-options) From b76f76675c8f0b5584349e1c73f64446f9f5b6a7 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 08:24:45 -0800 Subject: [PATCH 30/52] Update docs/choosing-technology/how-to-select-technology.md Co-authored-by: Monica Granbois --- docs/choosing-technology/how-to-select-technology.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/choosing-technology/how-to-select-technology.md b/docs/choosing-technology/how-to-select-technology.md index 8cd1675..572db6c 100644 --- a/docs/choosing-technology/how-to-select-technology.md +++ b/docs/choosing-technology/how-to-select-technology.md @@ -25,7 +25,7 @@ Column 1 lists the technology type. Column 2 lists the choices under that type. |Back-end| [Express](https://expressjs.com/), [NestJS](https://nestjs.com/), [Django](https://www.djangoproject.com/), [Flask](https://flask.palletsprojects.com/en/2.2.x/), [.NET Core](https://dotnet.microsoft.com/en-us/apps/aspnet), [Laravel](https://laravel.com/) |Front-end| [React](https://reactjs.org/), [Angular](https://angular.io/), [Vue](https://vuejs.org/)| |Code and artifact management| [GitHub](https://github.com/bcgov), [Artifactory](http://artifacts.developer.gov.bc.ca/), [GitHub Packages](https://docs.github.com/en/packages) -|Automation tools| [GitHub Actions](https://github.com/features/actions), [ArgoCD](https://argoproj.github.io/argo-cd/), [Terraform](https://www.terraform.io/), [Tekton/OpenShift Pipelines](https://tekton.dev/) +|Automation tools| [GitHub Actions](https://github.com/features/actions), [ArgoCD](/docs/default/component/platform-developer-docs/docs/automation-and-resiliency/argo-cd-usage/), [Terraform](https://www.terraform.io/), [Tekton/OpenShift Pipelines](/docs/default/component/platform-developer-docs/docs/build-deploy-and-maintain-apps/deploy-an-application/#1-integrate-deployment-into-a-cicd-pipeline) ### Hosting and operations Column 1 lists the technology type. Column 2 lists the choices under that type. From a97d65c95a2f387d4492ba45f49a1aea4ad8a5f9 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 08:25:01 -0800 Subject: [PATCH 31/52] Update docs/use-github-in-bcgov/remove-user-bcgov-github-access.md Co-authored-by: Monica Granbois --- docs/use-github-in-bcgov/remove-user-bcgov-github-access.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md b/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md index 974f4ba..a5dfa29 100644 --- a/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md +++ b/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md @@ -13,7 +13,7 @@ We have two steps to remove access: A GitHub user can access a team repo via GitHub team membership, or direct repo access. The GitHub help pages below offers guidance on how to complete removal: 1. [removing members from GitHub team(s)](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person) -2. [removing members from repo "Collaborators & teams" setting](https://docs.github.com/en/organizations/organizing-members-into-teams/removing-organization-members-from-a-team) +2. [removing members from repo "Collaborators & teams" setting](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person) ## Step 2: Remove membership in `bcgov` and/or `bcgov-c` orgs From 1a50bdd5a7bf8924c8cf447d21ecf8e2e96668bf Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 08:25:17 -0800 Subject: [PATCH 32/52] Update docs/index.md Co-authored-by: Monica Granbois --- docs/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/index.md b/docs/index.md index fbdf5f1..bc94073 100644 --- a/docs/index.md +++ b/docs/index.md @@ -7,7 +7,7 @@ The Developer Experience Team updates the BCDG. We've embedded links into our co ## 7 quick steps to get started 1. Bookmark the Developer Guide because it serves as the central hub for development matters. -2. [Bookmark the Mobile Developer's Guide](https://developer.gov.bc.ca/docs/default/component/mobile-developer-guide/mobile-developer-guide-introduction/) for guidance on building mobile applications. +2. Bookmark the [DevHub documentation page](https://developer.gov.bc.ca/docs?filters%5Buser%5D=all&limit=20) for a list of developer guides. 3. [Get access to the bcgov GitHub Organization](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/bc-government-organizations-in-github/#bcgov) - This organization is B.C. Government's default storage for code. - More information about `bcgov` and `bcgov-c` is available under [Organizations in GitHub](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/bc-government-organizations-in-github/#organizations-in-github) on the same page. From ff2c8687a6de7f94af4c96570d2109880c25e4d4 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 08:27:41 -0800 Subject: [PATCH 33/52] Update docs/use-github-in-bcgov/bc-government-organizations-in-github.md Co-authored-by: Monica Granbois --- .../bc-government-organizations-in-github.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md index c117366..d2a8d00 100644 --- a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md +++ b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md @@ -26,7 +26,7 @@ graph TD; A[GitHub Enterprise Cloud] --> B[bcgov]; A --> C[bcgov-c]; ``` -On July 2024, we enabled Single-Sign On **(SSO)** for `bcgov`. We enabled SSO for `bcgov-c` on August 2024. All members must be authenticated with IDIRs, including contractors. The [GitHub Single Sign-On (SSO) section](#single-sign-on) has more information about the transition. +In July 2024, we enabled Single-Sign On **(SSO)** for `bcgov`. We enabled SSO for `bcgov-c` in August 2024. All members must be authenticated with IDIRs, including contractors. The [GitHub Single Sign-On (SSO) section](#single-sign-on) has more information about the transition. To link GH accounts and IDIRs, [follow our SSO enablement instructions](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/bc-government-organizations-in-github/#directions-to-sign-up-and-link-your-account-for-bcgov). From e7149f2c052977b0c0e0771b75f3aba9ca30f98a Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 08:28:58 -0800 Subject: [PATCH 34/52] Update docs/use-github-in-bcgov/bc-government-organizations-in-github.md Co-authored-by: Monica Granbois --- .../bc-government-organizations-in-github.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md index d2a8d00..263f53c 100644 --- a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md +++ b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md @@ -12,7 +12,7 @@ With GiHub Enterprise Cloud, we can: The **Developer Experience team** manages B.C. Government's GitHub environments. For questions, concerns, or feedback, please [submit a support request on our Jira Service Manager system]( https://citz-do.atlassian.net/servicedesk/customer/portal/2). -For users who need quick access to common topics related to using GitHub in B.C. Government, please see the [GitHub for B.C. Government quick reference guide](docs/sample-govorginGH-quickref.md) instead of this doc. +For users who need quick access to common topics related to using GitHub in B.C. Government, please see the [GitHub for B.C. Government quick reference guide](quick-reference.md) instead of this doc. ## Organizations in GitHub From d6b43269097540821ae798cccee8c15b7d9ffbf3 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 08:29:17 -0800 Subject: [PATCH 35/52] Update docs/use-github-in-bcgov/bc-government-organizations-in-github.md Co-authored-by: Monica Granbois --- .../bc-government-organizations-in-github.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md index 263f53c..0ae7cc3 100644 --- a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md +++ b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md @@ -79,7 +79,7 @@ If the instructions and troubleshooting help below doesn't resolve any issues, p ### Security Insights for GitHub Enterprise-linked organizations -All orgs linked to the corporate GitHub Enterprise accounts have access to the Security Insight feature, inclusive of branch protection and code owners for private repos. +All orgs linked to the corporate GitHub Enterprise accounts have access to the [Security Insight feature](https://docs.github.com/en/enterprise-cloud@latest/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-security-insights), inclusive of branch protection and code owners for private repos. Branch protection allows specified members to push to the protected branch. The code owners feature allows automated reviews. For example, if a member is a code owner of certain files, they'll automatically be added as a PR reviewer. A PR needs their approval before the code can be merged. From f4063ff23fada867e2389bdf5cd67d8a01ac78ee Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 08:30:04 -0800 Subject: [PATCH 36/52] Update docs/use-github-in-bcgov/bc-government-organizations-in-github.md Co-authored-by: Monica Granbois --- .../bc-government-organizations-in-github.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md index 0ae7cc3..a59ef7a 100644 --- a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md +++ b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md @@ -81,7 +81,7 @@ If the instructions and troubleshooting help below doesn't resolve any issues, p All orgs linked to the corporate GitHub Enterprise accounts have access to the [Security Insight feature](https://docs.github.com/en/enterprise-cloud@latest/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-security-insights), inclusive of branch protection and code owners for private repos. -Branch protection allows specified members to push to the protected branch. The code owners feature allows automated reviews. For example, if a member is a code owner of certain files, they'll automatically be added as a PR reviewer. A PR needs their approval before the code can be merged. +[Branch protection](https://docs.github.com/en/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches) allows specified members to push to the protected branch. The [code owners feature](https://docs.github.com/en/enterprise-cloud@latest/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners) allows automated reviews. For example, if a member is a code owner of certain files, they'll automatically be added as a PR reviewer. A PR needs their approval before the code can be merged. ### Directions to sign up and link your account for `bcgov` From a85d9f88ccd29560f6cf54fad44ee84cc23f8485 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 08:30:54 -0800 Subject: [PATCH 37/52] Update docs/use-github-in-bcgov/github-transition-guide.md Co-authored-by: Monica Granbois --- docs/use-github-in-bcgov/github-transition-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-github-in-bcgov/github-transition-guide.md b/docs/use-github-in-bcgov/github-transition-guide.md index ed3b180..41a5e88 100644 --- a/docs/use-github-in-bcgov/github-transition-guide.md +++ b/docs/use-github-in-bcgov/github-transition-guide.md @@ -100,7 +100,7 @@ GitHub doesn't offer users a screen to confirm authentication. There are 2 alter ### Outside Collaborators -We discontinued the option to add outside collaborators. GitHub explains [more about outside collaborators on their doc](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/adding-outside-collaborators-to-repositories-in-your-organization). GitHub will send invitations to current outside collaborators to become full members on `bcgov`, and IDIRs are needed. +We discontinued the option to add outside collaborators. GitHub explains [more about outside collaborators on their doc](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/adding-outside-collaborators-to-repositories-in-your-organization). To create IDIRs or have more information, please read [the IDIR guide section](#idir-transition-guide) of this doc From 57d40f4d4cb3f36cb2bcdd61ff9e200c4e50817a Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 08:31:31 -0800 Subject: [PATCH 38/52] Update docs/use-github-in-bcgov/github-transition-guide.md Co-authored-by: Monica Granbois --- docs/use-github-in-bcgov/github-transition-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-github-in-bcgov/github-transition-guide.md b/docs/use-github-in-bcgov/github-transition-guide.md index 41a5e88..8ebd73e 100644 --- a/docs/use-github-in-bcgov/github-transition-guide.md +++ b/docs/use-github-in-bcgov/github-transition-guide.md @@ -112,7 +112,7 @@ GitHub differs from other tools that use IDIR as the user account to access serv The reason is due to GitHub’s open source code community ecosystem. A part of our commitment to open government is the `bcgov` GitHub org. We set up GitHub accounts to be associated with many different repos and orgs because throughout their careers, developers contribute to many different open projects and organizations. -With the GitHub SSO upgrade, contractors and developers working in the `bcgov` GitHub org will continue to use their GitHub to login to access GitHub. The extra step is the prompt to login to IDIR so we comply with security policies. +Contractors and developers working in the `bcgov` GitHub org use their GitHub account to login to access GitHub. The extra step is the prompt to login to IDIR so we comply with security policies. ### Resetting GitHub Keys From 1eab0ee363dcad36b19288d1a98f114e8f15a364 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 08:32:18 -0800 Subject: [PATCH 39/52] Update docs/use-github-in-bcgov/remove-user-bcgov-github-access.md Co-authored-by: Monica Granbois --- docs/use-github-in-bcgov/remove-user-bcgov-github-access.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md b/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md index a5dfa29..39d45b4 100644 --- a/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md +++ b/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md @@ -12,7 +12,7 @@ We have two steps to remove access: A GitHub user can access a team repo via GitHub team membership, or direct repo access. The GitHub help pages below offers guidance on how to complete removal: -1. [removing members from GitHub team(s)](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person) +1. [removing members from GitHub team(s)](https://docs.github.com/en/organizations/organizing-members-into-teams/removing-organization-members-from-a-team) 2. [removing members from repo "Collaborators & teams" setting](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person) ## Step 2: Remove membership in `bcgov` and/or `bcgov-c` orgs From f7f1b0b6862115f57bd890bc939eb8ec5af38ae5 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 08:32:50 -0800 Subject: [PATCH 40/52] Update docs/use-github-in-bcgov/license-your-github-repository.md Co-authored-by: Monica Granbois --- docs/use-github-in-bcgov/license-your-github-repository.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-github-in-bcgov/license-your-github-repository.md b/docs/use-github-in-bcgov/license-your-github-repository.md index c03861f..57e22ad 100644 --- a/docs/use-github-in-bcgov/license-your-github-repository.md +++ b/docs/use-github-in-bcgov/license-your-github-repository.md @@ -6,7 +6,7 @@ The Intellectual Property Program **(IPP)** must approve licences of B.C. Govern When IPP is the authority for the licensing, teams must work with IPP to find the best fit to meet the licensing needs of the project. -IPP examines the development history of the content, somtetimes in the form of a conversation. Initial questions include the following: +IPP examines the development history of the content, sometimes in the form of a conversation. Initial questions include the following: - Is the content created solely by B.C. Government employees? From feea1f88fc395b77bffdb59b57516cfdbe9cf2a1 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 08:33:15 -0800 Subject: [PATCH 41/52] Update docs/use-github-in-bcgov/remove-user-bcgov-github-access.md Co-authored-by: Monica Granbois --- docs/use-github-in-bcgov/remove-user-bcgov-github-access.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md b/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md index 39d45b4..471e977 100644 --- a/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md +++ b/docs/use-github-in-bcgov/remove-user-bcgov-github-access.md @@ -5,7 +5,7 @@ Removing a member's access should only occur when members don't work for the gov We have two steps to remove access: 1. [Remove their access to team repos](https://docs.github.com/en/organizations/organizing-members-into-teams/removing-organization-members-from-a-team). -2. [Remove membership in `bcgov` and/or `bcgov-c` orgs](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person). +2. Remove membership in `bcgov` and/or `bcgov-c` orgs ## Step 1: Remove access to team repos From 246a53cc9da1a51b9e1a0cbe03933de649ea2cde Mon Sep 17 00:00:00 2001 From: Monica Granbois Date: Tue, 20 Jan 2026 09:03:06 -0800 Subject: [PATCH 42/52] deleted unused file and updated whitespace in mkdocs.yml file --- docs/use-github-in-bcgov/github-security.md | 35 --------------------- mkdocs.yml | 4 +-- 2 files changed, 2 insertions(+), 37 deletions(-) delete mode 100644 docs/use-github-in-bcgov/github-security.md diff --git a/docs/use-github-in-bcgov/github-security.md b/docs/use-github-in-bcgov/github-security.md deleted file mode 100644 index 9373999..0000000 --- a/docs/use-github-in-bcgov/github-security.md +++ /dev/null @@ -1,35 +0,0 @@ -# Security Features for BC Government GitHub users - -The BC government GitHub organizations (`bcgov` and `bcgov-c`) have various security features available to help protect the code and repositories within them. This page will highlight some of these features and provide recommendations on using them for BC government development teams. - -## Availability - -The features described here are available and enabled in both `bcgov` and `bcgov-c` organizations. - -## Cost - -In the `bcgov` organization, there is no cost for these security features because all repositories are public, and GitHub provides them for free for public repositories. - -In the `bcgov-c` organization, there is a cost for these features since the repositories are private, and GitHub charges a fee for private repositories. However, this cost is currently covered by the Developer Experience Team, so individual teams or ministries do not need to pay. - -## Features - -The following features are some of the major security features available in the BC government GitHub organizations: - -- [Code scanning](https://docs.github.com/en/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning): This feature scans code for security vulnerabilities and coding errors. -- [Secret scanning](https://docs.github.com/en/code-security/secret-scanning/introduction/about-secret-scanning): This feature scans repositories and commits for sensitive information such as API keys, passwords, and other secrets. -- [Dependabot](https://docs.github.com/en/code-security/dependabot): This feature scans repositories for outdated or vulnerable dependencies and provides recommendations for fixing problems, including via automated pull requests. - -## Recommendations - -Application and code security are a complex topics, and the features described above are just a few of the many tools available to help teams secure their code. The Developer Experience Team has the following recommendations specific to these features provided within GitHub: - -- Keep the features enabled in your repositories. Even if some features can be reconfigured at the repository level, they are there to help you and your team secure your code. -- Use the Security Overview page for your repositories to see any issues detected by GitHub's security features. The Security Overview page is available in the repository under the "Security" tab. -- If you work on multiple repositories within `bcgov` or `bcgov-c`, you can use the [Security Overview for the organization](https://github.com/orgs/bcgov/security/overview) to see a summary of all security issues across multiple repositories in the organization. -- Take action on any issue surfaced by GitHub security features as soon as possible. The sooner you address issues - even if they are false positives that you dismiss without changes - the less likely they are to become a problem or become "noise" that you ignore. - - - - - diff --git a/mkdocs.yml b/mkdocs.yml index 8086c22..f241b37 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -48,11 +48,11 @@ nav: - Developing better questions: rocketchat/get-help-in-rocketchat.md - Quickstart Wizards: - - Quickstart for OpenShift Wizard: wizards/quickstart-for-openshift-wizard.md + - Quickstart for OpenShift Wizard: wizards/quickstart-for-openshift-wizard.md - DevHub Content Partner Guide: content-partner-guide.md - DevHub Content Syntax Guide: content-syntax-guide.md - Working with data: working-with-data.md - - BC Government API Guidelines: bc-government-api-guidelines.md + - BC Government API Guidelines: bc-government-api-guidelines.md # - Developer community: developer_community.md # - Application lifecycle: application_lifecycle.md From 940d7a243b2b13ac4b8905ac179f219aae2a31da Mon Sep 17 00:00:00 2001 From: Monica Granbois Date: Tue, 20 Jan 2026 09:06:13 -0800 Subject: [PATCH 43/52] fixed accessibility mkdocs section --- mkdocs.yml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/mkdocs.yml b/mkdocs.yml index f241b37..d9fda78 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -28,8 +28,9 @@ nav: - Security and Privacy: - Security and Privacy guidance: security/security-and-privacy-compliance-and-guidance.md - Security best practices for apps: security/best-practices-for-apps.md - - Accessibility: accessibility-resources.md - - The design system: design-system/about-the-design-system.md + - Accessibility: + - Accessibility: accessibility-resources.md + - The design system: design-system/about-the-design-system.md - GitHub in the B.C. government: - B.C. Government GitHub Quick Reference: use-github-in-bcgov/quick-reference.md - bcgov, bcgov-c, and SSO: use-github-in-bcgov/bc-government-organizations-in-github.md From 1be5d8ac391149434e26fedd2eb42ba7f907bbd2 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 10:04:08 -0800 Subject: [PATCH 44/52] Update index.md --- docs/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/index.md b/docs/index.md index bc94073..2aab395 100644 --- a/docs/index.md +++ b/docs/index.md @@ -8,12 +8,12 @@ The Developer Experience Team updates the BCDG. We've embedded links into our co 1. Bookmark the Developer Guide because it serves as the central hub for development matters. 2. Bookmark the [DevHub documentation page](https://developer.gov.bc.ca/docs?filters%5Buser%5D=all&limit=20) for a list of developer guides. -3. [Get access to the bcgov GitHub Organization](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/bc-government-organizations-in-github/#bcgov) - - This organization is B.C. Government's default storage for code. +3. [Get access to the bcgov GitHub Organization](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/bc-government-organizations-in-github/#bcgov) and - More information about `bcgov` and `bcgov-c` is available under [Organizations in GitHub](https://developer.gov.bc.ca/docs/default/component/bc-developer-guide/use-github-in-bcgov/bc-government-organizations-in-github/#organizations-in-github) on the same page. 4. [Bookmark the Developer Experience Jira Service Management](https://citz-do.atlassian.net/servicedesk/customer/portal/2) system, which is shortened to JSM. Users can submit support tickets -5. [Get access to GitHub Discussions](https://github.com/bcgov/bcgov-community-discussions). - - The developer community gathers here to ask questions, support each other with issues, and finds it the best source of support for internal serivces, such as cloud services and common components. +5. [Get access to GitHub Discussions](https://github.com/bcgov/bcgov-community-discussions) and [internal Rocket.Chat](https://chat.developer.gov.bc.ca/) + - Rocket.Chat is undergoing a migration and will become inactive soon. + - The developer community gathers on GitHub Discussion to ask questions, support each other with issues, and finds it the best source of support for internal serivces, such as cloud services and common components. 6. Explore [our internal services](https://digital.gov.bc.ca/technology/common-components/) and [Software-as-a-Service **(SaaS)** tools](https://digital.gov.bc.ca/technology/cloud/saas/) to support development. 7. Learn about what's happening in the [BC Gov Digital Ecosystem](https://digital.gov.bc.ca/blog/). From 186a3087a8808b59390c530d039432875fb31f16 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 10:10:37 -0800 Subject: [PATCH 45/52] Update privacy guidelines for public repositories Clarified guidelines on posting personal information in public repositories. --- docs/use-github-in-bcgov/evaluate-open-source-content.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-github-in-bcgov/evaluate-open-source-content.md b/docs/use-github-in-bcgov/evaluate-open-source-content.md index 5288a43..fae44a2 100644 --- a/docs/use-github-in-bcgov/evaluate-open-source-content.md +++ b/docs/use-github-in-bcgov/evaluate-open-source-content.md @@ -16,7 +16,7 @@ The [First steps working in GitHub doc](https://developer.gov.bc.ca/docs/default ## Privacy -Personal information **(P.I.)**, like name, phone number, photo, address, driver's license numbers, etc., must not be posted in public repos. Teams should contact their privacy analyst for help in privacy assessments. +Data shouldn't be posted into repos, only code. Personal information **(P.I.)**, like name, phone number, photo, address, driver's license numbers, etc., is data. Teams should contact their privacy analyst for help with privacy assessments. ## Security From bdca4da6b6dc90f68c07542ad809ad7d58e25dc4 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 10:14:36 -0800 Subject: [PATCH 46/52] Update IDIR guide section reference for clarity Clarified the IDIR guide section reference in the transition guide. --- docs/use-github-in-bcgov/github-transition-guide.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/use-github-in-bcgov/github-transition-guide.md b/docs/use-github-in-bcgov/github-transition-guide.md index 8ebd73e..d6c9d61 100644 --- a/docs/use-github-in-bcgov/github-transition-guide.md +++ b/docs/use-github-in-bcgov/github-transition-guide.md @@ -102,9 +102,7 @@ GitHub doesn't offer users a screen to confirm authentication. There are 2 alter We discontinued the option to add outside collaborators. GitHub explains [more about outside collaborators on their doc](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/adding-outside-collaborators-to-repositories-in-your-organization). -To create IDIRs or have more information, please read [the IDIR guide section](#idir-transition-guide) of this doc - -All accesses will stay the same. +To create IDIRs or have more information, please read [the IDIR guide section](#idir-transition-guide) of this doc. ### No new GitHub ID needed From 4ba7f9960e784d97060dffd424f04bbf9081bbb6 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 10:43:08 -0800 Subject: [PATCH 47/52] Update bc-government-organizations-in-github.md --- .../bc-government-organizations-in-github.md | 39 +++++++++---------- 1 file changed, 18 insertions(+), 21 deletions(-) diff --git a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md index a59ef7a..9c590dc 100644 --- a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md +++ b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md @@ -88,8 +88,13 @@ All orgs linked to the corporate GitHub Enterprise accounts have access to the [ 1. Have any two-factor device, and personal GitHub login and IDIR login ready. 2. Log into GitHub with your personal login. 3. [Authenticate your IDIR](https://github.com/orgs/bcgov/sso) -4. You'll get an email with an invitation to join the `bcgov` GitHub organization. The invitation will be sent to the email address associated with your GitHub account. - a. Refer to the [SSO troubleshooting section](#troubleshooting) if you didn't receive an email. +4. Go to [https://github.com](https://github.com). + - Sign in with the account used to join the [`bcgov` org](#directions-to-sign-up-and-link-your-account-for-bcgov) or [`bcgov-c` org](#directions-to-sign-up-and-link-your-account-for-bcgov-c). + - Click on your profile picture. + - Choose the "Your organizations" option from the menu. + - Confirm the `bcgov` and/or `bcgov-c` organization is listed under the "Organizations" page. + - Click the "Accept" button next to the organization. + - ![Screenshot of a user's organizations. The screen displays the `bcgov-c` organization with "Member" beside it. Next to it is "Invitation expires in 7 days" with Accept and Decline buttons.](../images/invitation.png) 5. Your teammates can add you to your team's repositories. We recommend teams use the [GitHub teams page](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. 6. [Authorize your personal access tokens and/or SSH keys](github-transition-guide.md#resetting-github-keys). @@ -100,12 +105,17 @@ That’s it, both accounts are now joined. A similar process applies for `bcgov-c`. 1. Have any two-factor devices, and personal GitHub login and IDIR login ready. -1. Log into GitHub with your personal login. -1. [Authenticate your IDIR](https://github.com/orgs/bcgov-c/sso) -1. You'll get an email with an invitation to join the `bcgov-c` GitHub organization. The invitation will be sent to the email address associated with your GitHub account. - 1. Refer to the [SSO troubleshooting section](#troubleshooting) if you didn't receive an email. -1. Your teammates can add you to your team's repositories. We recommend teams use [GitHub teams page](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. -1. [Re-authorize your personal access tokens and/or SSH keys](github-transition-guide.md#resetting-github-keys). +2. Log into GitHub with your personal login. +3. [Authenticate your IDIR](https://github.com/orgs/bcgov-c/sso) +4. Go to [https://github.com](https://github.com). + - Sign in with the account used to join the [`bcgov` org](#directions-to-sign-up-and-link-your-account-for-bcgov) or [`bcgov-c` org](#directions-to-sign-up-and-link-your-account-for-bcgov-c). + - Click on your profile picture. + - Choose the "Your organizations" option from the menu. + - Confirm the `bcgov` and/or `bcgov-c` organization is listed under the "Organizations" page. + - Click the "Accept" button next to the organization. + - ![Screenshot of a user's organizations. The screen displays the `bcgov-c` organization with "Member" beside it. Next to it is "Invitation expires in 7 days" with Accept and Decline buttons.](../images/invitation.png) +5. Your teammates can add you to your team's repositories. We recommend teams use [GitHub teams page](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. +6. [Re-authorize your personal access tokens and/or SSH keys](github-transition-guide.md#resetting-github-keys). That’s it, both accounts are now joined. @@ -120,16 +130,3 @@ That’s it, both accounts are now joined. allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen> - -### Troubleshooting - -If you didn't get an email invitation to join either organizations, you can check your organization status and invites: - -1. Go to [https://github.com](https://github.com). -1. Sign in with the account used to join the [`bcgov` org](#directions-to-sign-up-and-link-your-account-for-bcgov) or [`bcgov-c` org](#directions-to-sign-up-and-link-your-account-for-bcgov-c). -1. Click on your profile picture. -1. Choose the "Your organizations" option from the menu. -1. Confirm the `bcgov` and/or `bcgov-c` organization is listed under the "Organizations" page. -1. Click the "Accept" button next to the organization. - -![Screenshot of a user's organizations. The screen displays the `bcgov-c` organization with "Member" beside it. Next to it is "Invitation expires in 7 days" with Accept and Decline buttons.](../images/invitation.png) From 5a2d99ce80e2ae4cc8e8489d7dcf7c37b47231f9 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 10:44:31 -0800 Subject: [PATCH 48/52] Revise GitHub Apps request process Updated instructions for requesting GitHub Apps installation. --- .../start-working-in-bcgov-github-organization.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/use-github-in-bcgov/start-working-in-bcgov-github-organization.md b/docs/use-github-in-bcgov/start-working-in-bcgov-github-organization.md index e336ea8..d68f276 100644 --- a/docs/use-github-in-bcgov/start-working-in-bcgov-github-organization.md +++ b/docs/use-github-in-bcgov/start-working-in-bcgov-github-organization.md @@ -40,9 +40,7 @@ Active project needs appropriate processes and terms to manage contributions. ### Integrating GitHub Apps -We get large volumes of asks about adding GitHub Apps to our org's repos. Request a GitHub App to be installed from the **BCDevOps Requests Issue: Request for integrating a GitHub App**. - -If the available applications don't work for the team, please create an issue. We need: +We get large volumes of asks about adding GitHub Apps to our org's repos. [Submit a support request on our Jira Service Manager system] to request a GitHub App to be installed. We need to know: * Contact information From 1f18bf0fbd5c75737e80994e6aba5cd427c60cb4 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 11:12:55 -0800 Subject: [PATCH 49/52] Add Spring Boot to programming languages list --- docs/choosing-technology/how-to-select-technology.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/choosing-technology/how-to-select-technology.md b/docs/choosing-technology/how-to-select-technology.md index 572db6c..7a8e721 100644 --- a/docs/choosing-technology/how-to-select-technology.md +++ b/docs/choosing-technology/how-to-select-technology.md @@ -21,7 +21,7 @@ Column 1 lists the technology type. Column 2 lists the choices under that type. |Type| Choice| |----| ------| -|Programming languages|[Python](https://github.com/bcgov?q=&type=all&language=python&sort=), [Javascript](https://github.com/bcgov?q=&type=all&language=javascript&sort=), [TypeScript](https://github.com/bcgov?q=&type=all&language=typescript&sort=), [Java](https://github.com/bcgov?q=&type=all&language=java&sort=), [R](https://github.com/bcgov?q=&type=all&language=r&sort=), [C#](https://github.com/bcgov?q=&type=all&language=c%23&sort=), [PHP](https://github.com/bcgov?q=&type=all&language=php&sort=) +|Programming languages|[Python](https://github.com/bcgov?q=&type=all&language=python&sort=), [Javascript](https://github.com/bcgov?q=&type=all&language=javascript&sort=), [TypeScript](https://github.com/bcgov?q=&type=all&language=typescript&sort=), [Spring Boot](https://spring.io/projects/spring-boot), [R](https://github.com/bcgov?q=&type=all&language=r&sort=), [C#](https://github.com/bcgov?q=&type=all&language=c%23&sort=), [PHP](https://github.com/bcgov?q=&type=all&language=php&sort=) |Back-end| [Express](https://expressjs.com/), [NestJS](https://nestjs.com/), [Django](https://www.djangoproject.com/), [Flask](https://flask.palletsprojects.com/en/2.2.x/), [.NET Core](https://dotnet.microsoft.com/en-us/apps/aspnet), [Laravel](https://laravel.com/) |Front-end| [React](https://reactjs.org/), [Angular](https://angular.io/), [Vue](https://vuejs.org/)| |Code and artifact management| [GitHub](https://github.com/bcgov), [Artifactory](http://artifacts.developer.gov.bc.ca/), [GitHub Packages](https://docs.github.com/en/packages) From 05a8db9871ae9a225bd7bb35c463dc632dff86ea Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 11:24:20 -0800 Subject: [PATCH 50/52] Fix numbering and formatting in GitHub sign-up guide --- .../bc-government-organizations-in-github.md | 44 +++++++++---------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md index 9c590dc..b1b5936 100644 --- a/docs/use-github-in-bcgov/bc-government-organizations-in-github.md +++ b/docs/use-github-in-bcgov/bc-government-organizations-in-github.md @@ -86,17 +86,17 @@ All orgs linked to the corporate GitHub Enterprise accounts have access to the [ ### Directions to sign up and link your account for `bcgov` 1. Have any two-factor device, and personal GitHub login and IDIR login ready. -2. Log into GitHub with your personal login. -3. [Authenticate your IDIR](https://github.com/orgs/bcgov/sso) -4. Go to [https://github.com](https://github.com). - - Sign in with the account used to join the [`bcgov` org](#directions-to-sign-up-and-link-your-account-for-bcgov) or [`bcgov-c` org](#directions-to-sign-up-and-link-your-account-for-bcgov-c). - - Click on your profile picture. - - Choose the "Your organizations" option from the menu. - - Confirm the `bcgov` and/or `bcgov-c` organization is listed under the "Organizations" page. - - Click the "Accept" button next to the organization. - - ![Screenshot of a user's organizations. The screen displays the `bcgov-c` organization with "Member" beside it. Next to it is "Invitation expires in 7 days" with Accept and Decline buttons.](../images/invitation.png) -5. Your teammates can add you to your team's repositories. We recommend teams use the [GitHub teams page](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. -6. [Authorize your personal access tokens and/or SSH keys](github-transition-guide.md#resetting-github-keys). +1. Log into GitHub with your personal login. +1. [Authenticate your IDIR](https://github.com/orgs/bcgov/sso) +1. Go to [https://github.com](https://github.com). + - Sign in with the account used to join the [`bcgov` org](#directions-to-sign-up-and-link-your-account-for-bcgov) or [`bcgov-c` org](#directions-to-sign-up-and-link-your-account-for-bcgov-c). + - Click on your profile picture. + - Choose the "Your organizations" option from the menu. + - Confirm the `bcgov` and/or `bcgov-c` organization is listed under the "Organizations" page. + - Click the "Accept" button next to the organization. + - ![Screenshot of a user's organizations. The screen displays the `bcgov-c` organization with "Member" beside it. Next to it is "Invitation expires in 7 days" with Accept and Decline buttons.](../images/invitation.png) +1. Your teammates can add you to your team's repositories. We recommend teams use the [GitHub teams page](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. +1. [Authorize your personal access tokens and/or SSH keys](github-transition-guide.md#resetting-github-keys). That’s it, both accounts are now joined. @@ -105,17 +105,17 @@ That’s it, both accounts are now joined. A similar process applies for `bcgov-c`. 1. Have any two-factor devices, and personal GitHub login and IDIR login ready. -2. Log into GitHub with your personal login. -3. [Authenticate your IDIR](https://github.com/orgs/bcgov-c/sso) -4. Go to [https://github.com](https://github.com). - - Sign in with the account used to join the [`bcgov` org](#directions-to-sign-up-and-link-your-account-for-bcgov) or [`bcgov-c` org](#directions-to-sign-up-and-link-your-account-for-bcgov-c). - - Click on your profile picture. - - Choose the "Your organizations" option from the menu. - - Confirm the `bcgov` and/or `bcgov-c` organization is listed under the "Organizations" page. - - Click the "Accept" button next to the organization. - - ![Screenshot of a user's organizations. The screen displays the `bcgov-c` organization with "Member" beside it. Next to it is "Invitation expires in 7 days" with Accept and Decline buttons.](../images/invitation.png) -5. Your teammates can add you to your team's repositories. We recommend teams use [GitHub teams page](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. -6. [Re-authorize your personal access tokens and/or SSH keys](github-transition-guide.md#resetting-github-keys). +1. Log into GitHub with your personal login. +1. [Authenticate your IDIR](https://github.com/orgs/bcgov-c/sso) +1. Go to [https://github.com](https://github.com). + - Sign in with the account used to join the [`bcgov` org](#directions-to-sign-up-and-link-your-account-for-bcgov) or [`bcgov-c` org](#directions-to-sign-up-and-link-your-account-for-bcgov-c). + - Click on your profile picture. + - Choose the "Your organizations" option from the menu. + - Confirm the `bcgov` and/or `bcgov-c` organization is listed under the "Organizations" page. + - Click the "Accept" button next to the organization. + - ![Screenshot of a user's organizations. The screen displays the `bcgov-c` organization with "Member" beside it. Next to it is "Invitation expires in 7 days" with Accept and Decline buttons.](../images/invitation.png) +1. Your teammates can add you to your team's repositories. We recommend teams use [GitHub teams page](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) to manage access. +1. [Re-authorize your personal access tokens and/or SSH keys](github-transition-guide.md#resetting-github-keys). That’s it, both accounts are now joined. From c71984386c56a59157431f7e3b55c84adebd691d Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 11:32:52 -0800 Subject: [PATCH 51/52] Rearrange back-end technology options Reordered back-end technologies in the selection table. --- docs/choosing-technology/how-to-select-technology.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/choosing-technology/how-to-select-technology.md b/docs/choosing-technology/how-to-select-technology.md index 7a8e721..ad88274 100644 --- a/docs/choosing-technology/how-to-select-technology.md +++ b/docs/choosing-technology/how-to-select-technology.md @@ -22,7 +22,7 @@ Column 1 lists the technology type. Column 2 lists the choices under that type. |Type| Choice| |----| ------| |Programming languages|[Python](https://github.com/bcgov?q=&type=all&language=python&sort=), [Javascript](https://github.com/bcgov?q=&type=all&language=javascript&sort=), [TypeScript](https://github.com/bcgov?q=&type=all&language=typescript&sort=), [Spring Boot](https://spring.io/projects/spring-boot), [R](https://github.com/bcgov?q=&type=all&language=r&sort=), [C#](https://github.com/bcgov?q=&type=all&language=c%23&sort=), [PHP](https://github.com/bcgov?q=&type=all&language=php&sort=) -|Back-end| [Express](https://expressjs.com/), [NestJS](https://nestjs.com/), [Django](https://www.djangoproject.com/), [Flask](https://flask.palletsprojects.com/en/2.2.x/), [.NET Core](https://dotnet.microsoft.com/en-us/apps/aspnet), [Laravel](https://laravel.com/) +|Back-end| [Django](https://www.djangoproject.com/), [Flask](https://flask.palletsprojects.com/en/2.2.x/), [Express](https://expressjs.com/), [NestJS](https://nestjs.com/), [Spring Boot](https://spring.io/projects/spring-boot)[.NET Core](https://dotnet.microsoft.com/en-us/apps/aspnet), [Laravel](https://laravel.com/) |Front-end| [React](https://reactjs.org/), [Angular](https://angular.io/), [Vue](https://vuejs.org/)| |Code and artifact management| [GitHub](https://github.com/bcgov), [Artifactory](http://artifacts.developer.gov.bc.ca/), [GitHub Packages](https://docs.github.com/en/packages) |Automation tools| [GitHub Actions](https://github.com/features/actions), [ArgoCD](/docs/default/component/platform-developer-docs/docs/automation-and-resiliency/argo-cd-usage/), [Terraform](https://www.terraform.io/), [Tekton/OpenShift Pipelines](/docs/default/component/platform-developer-docs/docs/build-deploy-and-maintain-apps/deploy-an-application/#1-integrate-deployment-into-a-cicd-pipeline) From 13bb8e5f7486797b3ccaf145312d1f909707e490 Mon Sep 17 00:00:00 2001 From: Shivanganii <60671629+Shivanganii@users.noreply.github.com> Date: Tue, 20 Jan 2026 15:38:22 -0800 Subject: [PATCH 52/52] Update docs/choosing-technology/how-to-select-technology.md Co-authored-by: Monica Granbois --- docs/choosing-technology/how-to-select-technology.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/choosing-technology/how-to-select-technology.md b/docs/choosing-technology/how-to-select-technology.md index ad88274..867a272 100644 --- a/docs/choosing-technology/how-to-select-technology.md +++ b/docs/choosing-technology/how-to-select-technology.md @@ -21,7 +21,7 @@ Column 1 lists the technology type. Column 2 lists the choices under that type. |Type| Choice| |----| ------| -|Programming languages|[Python](https://github.com/bcgov?q=&type=all&language=python&sort=), [Javascript](https://github.com/bcgov?q=&type=all&language=javascript&sort=), [TypeScript](https://github.com/bcgov?q=&type=all&language=typescript&sort=), [Spring Boot](https://spring.io/projects/spring-boot), [R](https://github.com/bcgov?q=&type=all&language=r&sort=), [C#](https://github.com/bcgov?q=&type=all&language=c%23&sort=), [PHP](https://github.com/bcgov?q=&type=all&language=php&sort=) +|Programming languages|[Python](https://github.com/bcgov?q=&type=all&language=python&sort=), [Javascript](https://github.com/bcgov?q=&type=all&language=javascript&sort=), [TypeScript](https://github.com/bcgov?q=&type=all&language=typescript&sort=), [Java](https://github.com/bcgov?q=&type=all&language=java&sort=), [R](https://github.com/bcgov?q=&type=all&language=r&sort=), [C#](https://github.com/bcgov?q=&type=all&language=c%23&sort=), [PHP](https://github.com/bcgov?q=&type=all&language=php&sort=) |Back-end| [Django](https://www.djangoproject.com/), [Flask](https://flask.palletsprojects.com/en/2.2.x/), [Express](https://expressjs.com/), [NestJS](https://nestjs.com/), [Spring Boot](https://spring.io/projects/spring-boot)[.NET Core](https://dotnet.microsoft.com/en-us/apps/aspnet), [Laravel](https://laravel.com/) |Front-end| [React](https://reactjs.org/), [Angular](https://angular.io/), [Vue](https://vuejs.org/)| |Code and artifact management| [GitHub](https://github.com/bcgov), [Artifactory](http://artifacts.developer.gov.bc.ca/), [GitHub Packages](https://docs.github.com/en/packages)