nhcarrigan/maribelle
2
0
Fork 0
generated from nhcarrigan/template
Code Issues 3 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

WIP: feat: add a database client #3

Draft
nerdychara wants to merge 1 commits from feat/add-database into main
pull from: feat/add-database
merge into: nhcarrigan:main
Conversation 1 Commits 1 Files Changed 8 +174 -6
nerdychara commented 2025-07-02 07:55:32 -07:00
Member
Copy Link

Explanation

Mirabelle needs a database to be added rather than just use hard-coded values.

This will break and should not be merged at minimum until the environment variable is set to a value you want to use.

Issue

1

Attestations

Dependencies

  • I have pinned the dependencies to a specific patch version.

Style

  • I have run the linter and resolved any errors.
  • My pull request uses an appropriate title, matching the conventional commit standards.
  • My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request.

Tests

  • My contribution adds new code, and I have added tests to cover it.
  • My contribution modifies existing code, and I have updated the tests to reflect these changes.
  • All new and existing tests pass locally with my changes.
  • Code coverage remains at or above the configured threshold.

Documentation

No response

Versioning

Major - My pull request introduces a breaking change.

### Explanation Mirabelle needs a database to be added rather than just use hard-coded values. This will break and should not be merged at minimum until the environment variable is set to a value you want to use. ### Issue 1 ### Attestations - [x] I have read and agree to the [Code of Conduct](https://docs.nhcarrigan.com/community/coc/) - [x] I have read and agree to the [Community Guidelines](https://docs.nhcarrigan.com/community/guide/). - [x] My contribution complies with the [Contributor Covenant](https://docs.nhcarrigan.com/dev/covenant/). ### Dependencies - [x] I have pinned the dependencies to a specific patch version. ### Style - [x] I have run the linter and resolved any errors. - [x] My pull request uses an appropriate title, matching the conventional commit standards. - [x] My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request. ### Tests - [ ] My contribution adds new code, and I have added tests to cover it. - [ ] My contribution modifies existing code, and I have updated the tests to reflect these changes. - [ ] All new and existing tests pass locally with my changes. - [x] Code coverage remains at or above the configured threshold. ### Documentation _No response_ ### Versioning Major - My pull request introduces a breaking change.
nerdychara added 1 commit 2025-07-02 07:55:33 -07:00
feat: add a database client
Some checks failed
Node.js CI / Lint and Test (pull_request) Failing after 11s
Details
7e9dc20632
naomi added the
status
blocked
 label 2025-07-02 10:06:27 -07:00
naomi commented 2025-07-02 10:06:54 -07:00
Owner
Copy Link

This is blocked as the related issue has not been triaged yet.

Additionally, we use Prisma for our database client.

This is blocked as the related issue has not been triaged yet. Additionally, we use Prisma for our database client.
Some checks failed
Node.js CI / Lint and Test (pull_request) Failing after 11s
Details
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feat/add-database:feat/add-database
git checkout feat/add-database
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
New-contributor friendly
contribute
help wanted
Open to participation from the community
contribute
mentorship
Reserved for someone in our mentorship programme
contribute
staff only
Restricted to project staff members
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
No Label
status
blocked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
naomi nerdychara
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/maribelle#3
No description provided.
Delete Branch "feat/add-database"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?