![]() ![]() Set up pull request automation so that updates to PRs change the status of linked Linear issues. You can link PRs to issues three ways: by including the issue ID in the branch name, adding the issue ID in the PR title, or prefacing an issue ID with a magic word in the PR description (e.g. Once you connect Linear with GitHub, you can start linking your GitHub pull requests to Linear issues. If you change your Linear team name/ID, you may need to reconfigure the Autolink settings. ![]() You need to add each team separately as they all have a different ID pattern. Where workspace corresponds to your workspace's URL and ID is the issue identifier key for your team. ENG-123) in PR descriptions or comment to links, you can enable this using GitHub's Autolink references feature. If you want to automatically resolve your Linear issue IDs (e.g. Linear doesn't currently support GitHub Enterprise Server but we're considering adding support for it. If you're using GitHub Enterprise Cloud and have IP Allow List security setting enabled, you'll also need to turn on Enable IP allow list configuration for installed GitHub Apps setting to enable Linear's GitHub integration. Currently, we support multiple organizations for the PR automation only you'll only be able to use commit linking with a single GitHub org. This will take you through the same flow as when you connected the first organization. Select the three dot menu in the Connect Linear with GitHub pull requests section (which should show Enabled) and choose the Connect new organization option. Once you've connected one GitHub organization, go back to the integration settings page. All teams in your workspace will be able to link to issues in the selected repositories. If you don't require GitHub organization-level access, then a repository administrator can install GitHub. If you want Linear to have organization-level access to GitHub, then a GitHub organization owner will need to install the app within Linear. It's easy to add or remove repositories later just visit settings through the Configure GitHub button from Linear's Github integration settings page. To enable GitHub, click Connect Linear with GitHub Pull Requests in integration settings and select which repositories you want to give Linear access to. The GitHub integration doesn't require much beyond authenticating to GitHub and choosing what statuses to apply when PRs are created, request review, and merged. Because when I go into the workdir/./temp folder, in both approaches, this path contains only what was checked out from repo2, and nothing from repo1.Go to Settings to enable the GitHub integration. The CMake file should come from the original repo1 but for whatever reason it seems to me that the checkout of repo2 after is overwriting repo1. ![]() protocol=ssh branch=main name=repo2 subdir=folder2/ \Ģ Create a new recipe inside folder2 that only does a checkout of the new repo - STRUCTUREįunny enough, with both approaches I have basically the same result, with a few differences:ĮRROR: project-0.1.2-r1 do_configure: Execution of '/workdir/./project/0.1.2-r1/temp/run.do_configure.835' failed with exit code 1:ĬMake Error: The source directory "/workdir/./project/0.1.2-r1/git" does not appear to contain CMakeLists.txt.ĮRROR: project-1-r1 do_configure: Execution of '/workdir/./project/1-r1/temp/run.do_configure.835' failed with exit code 1:ĬMake Error: The source directory "/workdir/./project/1-r1/git" does not appear to contain CMakeLists.txt. SRC_URI = " protocol=ssh branch=master name=repo1 \ Now I want to move everything under and including the files/ folder into a new repository and also do a checkout with bitbake, I have tried the two following methods:ġ: Edit the recipe.bb to checkout both repositories and try to use subdir parameter in SRC_URI: - STRUCTURE Recipe.bb does a checkout of a repository into folder1, configures that repo's project and this project uses the *.json files shown there. I have the following file structure: - STRUCTURE ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |