-
Notifications
You must be signed in to change notification settings - Fork 59
AI #1613: Change ChargeType reference to ChargeCategory #1616
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
shawnalpay
wants to merge
7
commits into
candidate_recommendation
Choose a base branch
from
1613_repair_chargetype_reference
base: candidate_recommendation
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
AI #1613: Change ChargeType reference to ChargeCategory #1616
shawnalpay
wants to merge
7
commits into
candidate_recommendation
from
1613_repair_chargetype_reference
Conversation
This file contains hidden or 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
…ecommendation branch (#1601)
Contributor
|
Approved by the group without objections or abstentions during the November 13 Members’ call. |
ijurica
approved these changes
Nov 20, 2025
A couple of consistency fixes for the value formats. --------- Co-authored-by: Joaquin <[email protected]>
We have added a new entry to the Status attribute of the FOCUS WG project view (`In Evaluation`) to represent the Feature Request Review process we have introduced to FOCUS 1.4. This PR updates the documentation for the Status attribute in the development processes guidelines. This PR is NOT to be approved and merged as part of 1.3, as it was not part of that release process. We can approve and merge in any Members meeting after Nov 6. --------- Co-authored-by: Joaquin Prado <[email protected]> Co-authored-by: Joaquin <[email protected]>
jpradocueva
approved these changes
Nov 21, 2025
Contributor
jpradocueva
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved by the Members on the November 13th call.
…1609) Add unittest to ensure no other similar issues found and to keep this happening again Signed-off-by: Mike Fuller <[email protected]> Co-authored-by: Joaquin <[email protected]>
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.