-
## Story
We actually have 3 verification levels possible which each have different use cases and tradeoffs. I have taken to calling this the "anchor" status. The signature will be valid, but the an…
-
This specs site should be merged into the main Firedancer repo.
Checking in docs improvements along with code changes is good practice,
and allows us to benefit from the Gerrit review process.
Qu…
riptl updated
2 years ago
-
Our organisation have implemented a Jenkins pipeline library. This library perform a JIRA integration. We implement a check at build time to force commit message template to refer issues of type defec…
-
We also need to come up with a clean way of pushing pull requests to master to keep the history clean.
Seems like that two (of three) options on the Github-App doesn't work as I expect them to 🤔
Will …
-
**Developer TODO (don't remove)**
- [ ] create new branch. put issue number at start of name
- [ ] update documentation
- [ ] squash and merge
- [ ] delete branch
Touch trigger to touch action,th…
-
**Developer TODO (don't remove)**
- [x] create new branch. put issue number at start of name
- [ ] write tests before working on feature. put issue number in comment
- [ ] do #698 first.
- [ ] sho…
-
When using Azure DevOps' squash merge feature, it adds a prefix of "Merged PR {nnn}: " to the PR title which itself it taken from the title of the first commit message associated with the request. Th…
-
I suggested that all branches could deploy to QA and we just get the most recently updated one, so that you can easily squash-merge changes when finished.
Show the commit ID on the website so we ca…
-
The `auto-submit` bot is dropping commit information when it lands PRs, instead duplicating the PR title both as the title and description (first and 3rd+ lines) of the commit message.
Like here:
…
-
**Developer TODO (don't remove)**
- [ ] create new branch. put issue number at start of name
- [ ] update documentation
- [ ] squash and merge
- [ ] delete branch
Some applications use differen…