-
Observed with my recent PR (https://github.com/valkey-io/valkey-io.github.io/pull/114) that we merge all the individual commits as part of merging a PR. This is different from github.com/valkey-io/val…
-
## Description
Document how we support workflows that utilize squashing and merging
### Page(s)
Might be a new page that specifically focused on how we support different merging workflows
### …
-
commits are linear chain of edits
a branch is an alternative timeline of commits
can merge branches back together
checkout dev branch as example
edits on dev and main
merge back to main
merge squash…
-
### Describe the bug
Maybe I missed it somewhere, but I couldn't find a clear description of how to accept a pull request. Squash instead of merge, right? And when squashing, don't leave all the i…
-
*as a user and developer it makes the most sense to see the latest releases on `main` rather than a branch called `selection-refactor`*
The way it is:
- `master` has previously used versions of wr…
e-lo updated
23 hours ago
-
## Deployment
AFAICT, currently there are no release branches for specific deployments so we could switch to a flow where stable versions are marked by tagging commits on the main branch.
We coul…
-
Hi,
Thanks for this useful tool! I tried to apply Cytocipher to my data but got an error in step `cc.tl.merge_clusters`
```py
Cell In[10], line 1
----> 1 cc.tl.merge_clusters(rna, new_anno, n_…
-
## Preserve PyPSA-Earth-Sec history
The MERGE PR has been mistakenly squashed and merged and now the entire history of the pypsa-earth-sec repo is not shown in the main pypsa-earth repo.
Su…
-
### Problem
The commit history for some source code files is not easy to read due to:
- more commits than associated pull requests
- commit messages that are not very descriptive
It looks to m…
-
Notes to include:
git stores diffs
commits as snapshot in time
revert a file or the whole project
git project is called a repo
lab notebook for code
commits are linear chain of edits
a branch is an …