Skip to content

making main verify public#69

Open
sean-sype-simmons wants to merge 1 commit intomainfrom
sean-sype-simmons/mainVerify
Open

making main verify public#69
sean-sype-simmons wants to merge 1 commit intomainfrom
sean-sype-simmons/mainVerify

Conversation

@sean-sype-simmons
Copy link
Copy Markdown
Collaborator

now that the repo is public we need to ensure the tests are public

Description

ensuring any fork'd pr's can be testable.

Related Issue

Types of changes

  • 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 change)
  • Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • I have run the pre-merge tests locally and they pass.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

now that the repo is public we need to ensure the tests are public

Signed-off-by: Sean Simmons <ssimmons@progress.com>
@nikhil2611 nikhil2611 added the Expeditor: Skip All Used to skip all merge_actions. label Mar 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Expeditor: Skip All Used to skip all merge_actions.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants