-
Building on https://github.com/Oxen-AI/Oxen/issues/138, it would be great if `oxen info --json ` were possible.
That would spit out the likes of:
```
{
resource: path/to/resource
branch…
-
**[Original report](https://bitbucket.org/motiondesign/aequery/issue/40) by Remco Janssen (Bitbucket: [Remco Janssen](https://bitbucket.org/Remco Janssen), ).**
--------------------------------------…
-
Recently Pushwoosh updated its Remote Guide API documentation, version `2.x.x` of the library should progressively implement the new requests.
- [ ] `/getMessageDetails` (http://docs.pushwoosh.com/d…
-
### I have searched through the issues and didn't find my problem.
- [X] Confirm
### Problem
Currently we are using a workflow similar to GitFlow and have two major branches: `master` and `develop`…
-
It is my understanding from the page http://nvie.com/posts/a-successful-git-branching-model/, where I first learned the git-flow model about 2 years ago, that a `tag` would always be on the commit whe…
-
If there is a `release` branch present (locally) and I `finish` a `hotfix` the resulting `master` branch should be merged into the `release` branch, too.
Currently the `hotfix` is only merged into `m…
havvg updated
4 years ago
-
We use shell scripts wrapping git flow release for our release processes. If the developer doing the release hasn't kept their local master pointing to the origin master, then `git flow release finish…
-
I have a suggestion for a extension to the functionality of bugfixes and to make them differ from feature branches.
When you finish a bugfix and have a active release, I think it would be a good idea …
-
Since #46 was added, my builds are all messed up now.
We push code from development, to qc, to staging, and finally production. We add a tag when we're ready to increment the version number in de…
-
Hey everyone,
## Team Repos
I talked to Joel and I think we're probably going to want to break each team off into their own repo for now, then work on combining code into one repo as necessary later …