feat(api): restrict transaction creation based on entitlement #365
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Sep 22, 2024
This was referenced Sep 22, 2024
Graphite Automations"Request reviewers once CI passes" took an action on this PR • (09/22/24)2 reviewers were added to this PR based on Dustin Do's automation. |
duongdev
changed the base branch from
09-22-feat_api_restrict_category_creation_based_on_entitlement
to
graphite-base/365
duongdev
force-pushed
the
09-22-feat_api_restrict_transaction_creation_based_on_entitlement
branch
from
bc6edd4 to
ef70ce8
Compare
duongdev
deleted the
09-22-feat_api_restrict_transaction_creation_based_on_entitlement
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.