Click on the “authorize gitpod-io” button. When you’re done checking off the permissions, click the “Update Permissions” button.Īnother tab might also appear where on GitHub’s end you accept the additional permissions Gitpod is requesting. It’s a good idea to check all of them off so you don’t need to go through this process again. In the list of Git Providers on the page, find GitHub, click the three dots next to the listing, and select “Edit Permissions” from the dropdown menu.Ī popup will appear with a list of permission checkboxes. You will get taken to the Integration section of Gitpod’s settings. Click the “open access control” button on the popup. If this happens, you will have to restart the fork creation process (publish branch -> say yes to creating a fork). You may also be asked to update the permissions you give Gitpod to access GitHub through a popup. On the popup, select the “create fork” button.ĭuring the process of fork creation, you may be prompted to grant GitHub access to Gitpod’s GitHub extension (you should allow this). A popup will appear, asking if you would like to make a fork and push to that instead.
Click on the “publish branch button” on the source control panel. However, as you will not have access to the main repository itself, you will be prompted to first create a fork. You can now publish your branch to the remote. A modal may appear asking you to first stage your changes. Back in the source control panel, you can make a commit message in the text box above the “commit button” in the section for the mattermost-webapp repository. Now that the branch has changed, you can commit your changes to it. A good name idea is to name it after the code that refers to your issue - in this case, this is the “Test Key”, so a suitable name for the branch is MM-T642. In the box that appears, name your new branch. Click the option that says: “+ Create new branch…” Next to the label for mattermost-webapp, click the button with the branch name and the source control icon.Ī dropdown will appear via the command palette. On the panel next to the side bar, you will see a list of the repositories in the workspace, and under each repository a list of the files that have changed (if any). Thus, you will need to bring the changes you’ve made over from the master or main branch to a new branch on your own fork of the repository.Ĭlick the “Source Control” icon on the left sidebar.
You most likely won’t have direct write access to the repository you are working on. The development process is very similar to how you would work locally. For example, you could be working on writing an End-to-End (E2E) test, like this issue Write Webapp E2E with Cypress: "MM-T642 Attachment does not collapse" #18184. Once Gitpod has done loading, the user interface presented is that of VSCode. You may need to sign in (through GitHub) to access the workspace on Gitpod. What the extension does is add a green Gitpod button to repository pages on GitHub, and clicking it spins up a new environment for the repository on Gitpod. You can also use the Gitpod browser extension to open up a repository in Gitpod, or manually prefix GitHub repository URLs with gitpod.io/#.□ Spinning up an environmentĬreate a new workspace for a ticket/issue that you’ve claimed by going to the mattermost-gitpod-config repository and clicking the “Open in Gitpod” badge. You can also check out these videos to learn how to work with Gitpod (and write an E2E test): How to set up a developer environment for Mattermost with Gitpod and Writing your first E2E test for Mattermost. The following instructions have been adapted from comments on this issue: Document general usage of Gitpod #18. Gitpod is a cloud development environment.