-
The git history is already looking a bit hairy due to merge commits. I propose that we change the github settings for this repository to default to 'rebase and merge'.
-
If a PR has several commits on the branch, `re` shows a diff that does not reflect all of the changes that make up the PR, but only a subset (the latest commit?).
This may be how git works and have…
-
### Reproduction steps
Apologies, my repro is using pygit2, but I would suspect this may be an underlying issue?
```py
from tempfile import mkdtemp
from pygit2 import init_repository, Signature
f…
-
tl:dr; Add a dedicated http REST CRUD API to manage Dashboards to support infra-as-code use-cases.
-----
**Current approach: using the saved object API**
Dashboards can be programmatically…
-
Not sure if this is something people do a lot or even should should do a lot. But if they do it, they should do it using Git Town. Because Git Town
- provides a workflow engine to do these complex …
-
- Should we require only one commit per Pull Request?
- Should we require squashing pull requests before merging?
- If we do require squashing how do we ensure that the commit message looks nice?
-…
-
First off, thank you for building spr! This is already proven to be a really helpful tool.
One workflow I wish could be improved is landing a whole approved stack. I'll often send out a few diffs i…
-
- [x] Submit a feature request to GitHub for "Stacked Reviews" #56635
- [ ] Define a workflow using the current feature set of Pull Requests that will provide similar functionality to Phabricator's "…
-
steps
- make change 1 in branch A (which has db changes)
- make change 2 in branch B (which has db changes)
- switch back to branch A to run code, get this error
```
> docker-compose -f docker…
-
We've been planning a move to Django 4.0 and haven't run into any showstoppers yet, however, on our admin pages, we've seen some unnecessary text showing up since the update. (Thanks for updating the …
gaige updated
2 years ago