Skip to content
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

Add optional previous GovActionId in some ProposalProcedures #3615

Merged
merged 3 commits into from
Aug 9, 2023

Conversation

lehins
Copy link
Collaborator

@lehins lehins commented Aug 7, 2023

Description

Fixes #3611

Implement PrevGovActionId and GovActionPurpose

  • Wrap PrevGovActionId in GovernanceActions with a StrictMaybe in
    order to account fo rthe fact that we will start in the state in which
    there are no governance action
  • Addition of GovActionPurpose is motivated by the fact that we
    distinguish between previous governance action. Eg. NoConfidence and
    NewCommittee are considered to have the same purpose, while other
    are distinct. This will protect us from mixing them up when checking in
    the governance state

Checklist

  • Commit sequence broadly makes sense and commits have useful messages
  • New tests are added if needed and existing tests are updated
  • When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
    versioning process.
  • The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
  • All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
  • Code is formatted with fourmolu (use scripts/fourmolize.sh)
  • Cabal files are formatted (use scripts/cabal-format.sh)
  • hie.yaml has been updated (use scripts/gen-hie.sh)
  • Self-reviewed the diff

@lehins lehins force-pushed the lehins/require-prev-govaction-id branch 3 times, most recently from 10b2a9b to a02bd38 Compare August 7, 2023 23:14
@lehins lehins force-pushed the lehins/require-prev-govaction-id branch from 3053037 to 16763bc Compare August 7, 2023 23:43
Copy link
Contributor

@aniketd aniketd left a comment

Choose a reason for hiding this comment

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

LGTM! 🙌

@lehins lehins force-pushed the lehins/require-prev-govaction-id branch from 16763bc to 0103a89 Compare August 8, 2023 22:54
@lehins lehins enabled auto-merge August 8, 2023 22:55
@lehins lehins force-pushed the lehins/require-prev-govaction-id branch from 0103a89 to 19fecd6 Compare August 9, 2023 09:40
@lehins lehins disabled auto-merge August 9, 2023 10:09
@lehins lehins enabled auto-merge August 9, 2023 10:10
@lehins lehins disabled auto-merge August 9, 2023 10:20
lehins added 3 commits August 9, 2023 13:56
* Wrap `PrevGovActionId` in `GovernanceActions` with a `StrictMaybe` in
  order to account fo rthe fact that we will start in the state in which
  there are no governance action
* Addition of `GovActionPurpose` is motivated by the fact that we
  distinguish between previous governance action. Eg. `NoConfidence` and
  `NewCommittee` are considered to have the same purpose, while other
  are distinct.
@lehins lehins force-pushed the lehins/require-prev-govaction-id branch from 19fecd6 to ef62e9c Compare August 9, 2023 11:56
@lehins lehins enabled auto-merge August 9, 2023 11:56
@lehins lehins merged commit d966921 into master Aug 9, 2023
@iohk-bors iohk-bors bot deleted the lehins/require-prev-govaction-id branch August 9, 2023 13:48
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.

Add previous governance action id to the proposal
2 participants