Lines Matching +full:- +full:- +full:github +full:- +full:branch

6 All new features should be uploaded as PRs against the `main` branch. 
8 Once merged into `main`, they will be automatically merged into the `snapshot` branch.
12 …ich depend on a `SNAPSHOT` versions of Jetpack Compose. These are built from the `snapshot` branch.
16 …e, updating to a new Compose snapshot is done by submitting a new PR against the `snapshot` branch:
20 # Create branch for PR
21 git checkout -b update_snapshot
26 Edit [`/gradle/libs.versions.toml`](https://github.com/google/accompanist/blob/main/gradle/libs.ver…
38 Now `git commit` the changes and push to GitHub.
40 Finally create a PR (with the base branch as `snapshot`) and send for review.
48 First we merge the `snapshot` branch into `main`:
54 # Create branch for PR
55 git checkout -b main_snapshot_merge
57 # Merge in the snapshot branch
63 Edit [`/gradle/libs.versions.toml`](https://github.com/google/accompanist/blob/main/gradle/libs.ver…
67 1. Update the `composesnapshot` property to a single character (usually `-`). This disables the sna…
68 2. Update the `compose` property to match the new release (i.e. `1.0.0-beta06`)
79 Edit [gradle.properties](https://github.com/google/accompanist/blob/main/gradle.properties):
81  * Update the `VERSION_NAME` property and remove the `-SNAPSHOT` suffix.
85 ### #4: Push to GitHub
87 Push the branch to GitHub and create a PR against the `main` branch, and send for review. Once appr…
91 Once the above PR has been approved and merged, we need to create the GitHub release:
93  * Open up the [Releases](https://github.com/google/accompanist/releases) page.
98 …rigger the docs action to run, which will auto-deploy a new version of the [website](https://googl…
104 Edit [gradle.properties](https://github.com/google/accompanist/blob/main/gradle.properties):
106 …* Update the `VERSION_NAME` property, by increasing the version number, and adding the `-SNAPSHOT`…
107  * Example: released version: `0.3.0`. Update to `0.3.1-SNAPSHOT`