Skip to content

Conversation

@capnrefsmmat
Copy link
Contributor

And updates to a couple old ones.

  • Unless it is a documentation hotfix it should be merged against the dev branch
  • Branch is up-to-date with the branch to be merged with, i.e. dev
  • Build is successful
  • Code is cleaned up and formatted

And updates to a couple old ones.
@capnrefsmmat capnrefsmmat requested review from a team and BrainIsDead and removed request for a team July 26, 2023 20:43
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@melange396
Copy link
Collaborator

this looks like it supercedes #1201... should we close that?

@capnrefsmmat
Copy link
Contributor Author

Oh... yes. I thought I had seen this publication earlier, but I didn't realize I had a PR for it.

@melange396 melange396 merged commit 5981446 into dev Jul 27, 2023
@melange396 melange396 deleted the ctis/pubs branch July 27, 2023 00:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants