Skip to content

Conversation

@kbventures
Copy link
Owner

Describe your changes

Issue ticket number and link

Name of Contributor

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • My code does not generate any new warnings or errors
  • New and existing unit tests pass locally with my changes (if relevant)

@kbventures kbventures linked an issue Jan 21, 2023 that may be closed by this pull request
@kbventures kbventures temporarily deployed to e-renaissance-pr-166 January 21, 2023 16:31 Inactive
@kbventures kbventures temporarily deployed to e-renaissance-pr-166 January 27, 2023 15:11 Inactive
@kbventures kbventures temporarily deployed to e-renaissance-pr-166 January 27, 2023 15:20 Inactive
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.

ISSUE-164-testing-pipeline

2 participants