Skip to content

Conversation

@frankdavid
Copy link
Contributor

This is a follow-up to #8558, addressing reviewer comments that were added after the submission and improving readability.

This is a follow-up to #8558, addressing reviewer comments that were added after the submission and improving readability.
@frankdavid frankdavid requested review from a team as code owners February 6, 2026 11:53
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This pull request changes code owned by the Governance team. Therefore, make sure that
you have considered the following (for Governance-owned code):

  1. Update unreleased_changelog.md (if there are behavior changes, even if they are
    non-breaking).

  2. Are there BREAKING changes?

  3. Is a data migration needed?

  4. Security review?

How to Satisfy This Automatic Review

  1. Go to the bottom of the pull request page.

  2. Look for where it says this bot is requesting changes.

  3. Click the three dots to the right.

  4. Select "Dismiss review".

  5. In the text entry box, respond to each of the numbered items in the previous
    section, declare one of the following:

  • Done.

  • $REASON_WHY_NO_NEED. E.g. for unreleased_changelog.md, "No
    canister behavior changes.", or for item 2, "Existing APIs
    behave as before.".

Brief Guide to "Externally Visible" Changes

"Externally visible behavior change" is very often due to some NEW canister API.

Changes to EXISTING APIs are more likely to be "breaking".

If these changes are breaking, make sure that clients know how to migrate, how to
maintain their continuity of operations.

If your changes are behind a feature flag, then, do NOT add entrie(s) to
unreleased_changelog.md in this PR! But rather, add entrie(s) later, in the PR
that enables these changes in production.

Reference(s)

For a more comprehensive checklist, see here.

GOVERNANCE_CHECKLIST_REMINDER_DEDUP

@github-actions github-actions bot added the fix label Feb 6, 2026
Copy link
Contributor

@jasonz-dfinity jasonz-dfinity left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM for adding Default to ProposalInfo

frankdavid and others added 2 commits February 12, 2026 11:04
@frankdavid frankdavid enabled auto-merge February 12, 2026 10:07
@frankdavid frankdavid added this pull request to the merge queue Feb 12, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Feb 12, 2026
@frankdavid frankdavid added this pull request to the merge queue Feb 12, 2026
Merged via the queue into master with commit 888e4d1 Feb 12, 2026
95 of 97 checks passed
@frankdavid frankdavid deleted the frankdavid/recovery-fixes branch February 12, 2026 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants