Skip to content

Conversation

@ocofaigh
Copy link
Contributor

@ocofaigh ocofaigh commented May 3, 2024

Description

Update repo name to stack-ibm-retrieval-augmented-generation to comply with the agreed naming prefix for stack (stack-ibm-).
Alternatively we could go with stack-ibm-rag ?

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

For mergers

  • Use a conventional commit message to set the release level. Follow the guidelines.
  • Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
  • Use the Squash and merge option.

@ocofaigh ocofaigh requested a review from vburckhardt May 3, 2024 10:06
@ocofaigh
Copy link
Contributor Author

ocofaigh commented May 3, 2024

@vburckhardt let me know what you think?

@vburckhardt
Copy link
Member

Perhaps we use the term da here rather than stack. It's a deployable architecture technically

@ocofaigh
Copy link
Contributor Author

@vburckhardt just getting back to this.. I went with stack-ibm- as the prefix since thats what we used with stack-ibm-template and stack-ibm-core-security-services. Were you proposing it should maybe start with da-ibm ? I guess I'm trying to make it obvious that these repos are not consumable entities (like a terraform based module or DA) but open to suggestions. Ideally lets close on this before more stacks repos are created.

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