Peerplays_Blockchain/peerplays_migrated
1
0
Fork 0
Code Issues 35 Pull requests 4 Projects Releases 20 Packages Wiki Activity Actions

Draft: #579 - Enable witness hardfork check #844

Open
vampik wants to merge 3 commits from feature/579-enable-hardfork-check into develop
pull from: feature/579-enable-hardfork-check
merge into: Peerplays_Blockchain:develop
Conversation 8 Commits 3 Files changed 2 +4 -2
vampik commented 2024-01-19 10:06:10 +00:00 (Migrated from gitlab.com)
Copy link

#579 - Enable witness hardfork check

#579 - Enable witness hardfork check
vampik commented 2024-01-19 10:06:11 +00:00 (Migrated from gitlab.com)
Copy link

requested review from @bobinson and @vampik

requested review from @bobinson and @vampik
vampik commented 2024-01-19 10:06:11 +00:00 (Migrated from gitlab.com)
Copy link

assigned to @vampik

assigned to @vampik
vampik commented 2024-01-22 04:52:12 +00:00 (Migrated from gitlab.com)
Copy link

added 8 commits

  • 87b4f4a2...96de2fb9 - 7 commits from branch develop
  • daf76741 - Merge branch 'develop' into feature/579-enable-hardfork-check

Compare with previous version

added 8 commits <ul><li>87b4f4a2...96de2fb9 - 7 commits from branch <code>develop</code></li><li>daf76741 - Merge branch &#39;develop&#39; into feature/579-enable-hardfork-check</li></ul> [Compare with previous version](/PBSA/peerplays/-/merge_requests/264/diffs?diff_id=900533412&start_sha=87b4f4a242ee2f5f80abf90fb667153b3f8b7571)
vampik commented 2024-01-22 06:09:39 +00:00 (Migrated from gitlab.com)
Copy link

added 1 commit

Compare with previous version

added 1 commit <ul><li>d787d754 - #579 - add missing hardforks</li></ul> [Compare with previous version](/PBSA/peerplays/-/merge_requests/264/diffs?diff_id=900563318&start_sha=daf7674152ef3d284c55db4035aebe98e5ae8f72)
bobinson commented 2024-01-22 10:01:21 +00:00 (Migrated from gitlab.com)
Copy link

requested review from @serkixenos

requested review from @serkixenos
bobinson commented 2024-01-22 10:01:51 +00:00 (Migrated from gitlab.com)
Copy link

hi @prandnum - Can you verify this functionality from your end ?

hi @prandnum - Can you verify this functionality from your end ?
vampik commented 2024-01-22 14:42:04 +00:00 (Migrated from gitlab.com)
Copy link

marked this merge request as draft

marked this merge request as **draft**
prandnum commented 2024-01-24 15:21:55 +00:00 (Migrated from gitlab.com)
Copy link

@bobinson please see the details here https://gitlab.com/PBSA/peerplays/-/issues/579

@bobinson please see the details here https://gitlab.com/PBSA/peerplays/-/issues/579
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feature/579-enable-hardfork-check:feature/579-enable-hardfork-check
git checkout feature/579-enable-hardfork-check

Merge

Merge the changes and update on Forgejo.
git checkout develop
git merge --no-ff feature/579-enable-hardfork-check
git checkout develop
git merge --ff-only feature/579-enable-hardfork-check
git checkout feature/579-enable-hardfork-check
git rebase develop
git checkout develop
git merge --no-ff feature/579-enable-hardfork-check
git checkout develop
git merge --squash feature/579-enable-hardfork-check
git checkout develop
git merge --ff-only feature/579-enable-hardfork-check
git checkout develop
git merge feature/579-enable-hardfork-check
git push origin develop
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
confirmed

   
DevOps

   
documentation

   
enhancement

   
incident

Denotes a disruption to IT services and the associated issues require immediate attention

  
Medium

   
priority::Critical

(optional) Issues that are marked as critical priority. Should be taken care of ASAP.

  
priority::High

(optional) Issues that are marked as high priority.

  
priority::Low

(optional) Issues that are marked as low priority.

  
priority::Medium

(optional) Issues that are marked as medium priority.

  
QA-TestCases::Done

QA-Labels

  
QA-TestCases::InProgress

QA-Labels

  
RNG

   
security

(optional) Issues that relate to the security of the project.

  
severity:: Critical

   
severity:: High

   
severity:: Low

   
severity:: Medium

   
state:: Accepted

Issues that are newly created and have been accepted after review.

  
state:: Blocked

Issues that cannot be worked on due to other factors linked to it.

  
state:: Done

Issues that are closed with a working solution.

  
state:: in progress

Issues that are currently being worked on.

  
state:: in review

Issues that require a proposed solution to be reviewed.

  
state:: on hold

Issues that were at least accepted, that should not be worked on at the moment.

  
state:: Pending

Issues that are newly created and haven't been reviewed.

  
state:: Pushed to Prod

Tickets are verified in the stage infra and needs to be deployed in the production

  
state:: Revision Needed

Issues that need to be revised before being accepted.

  
state::out-of-scope

Task and issues which are out of scope due to change in requirements

  
suggestion

   
support

   
To Do

   
type :: Discussion

   
type :: Duplicate

(optional) Issues that are duplicates of existing issues in the same project.

  
type:: interaction-design

   
type:: New Feature

Issues that bring new functionality to the project.

  
type::bug

BUG

  
type::documentation

Issues that relate to the documentation of the project.

  
type::incident

severe issues that require immediate response

  
type::maintenance

Issues that require maintenance on the project.

  
type::question

Issues that are questions related to the project.

  
type::recurring-tasks

This label is used to track recurring tasks which may repeat daily, weekly or monthly.

  
vulnerability
No labels
confirmed
DevOps
documentation
enhancement
incident
Medium
priority::Critical
priority::High
priority::Low
priority::Medium
QA-TestCases::Done
QA-TestCases::InProgress
RNG
security
severity:: Critical
severity:: High
severity:: Low
severity:: Medium
state:: Accepted
state:: Blocked
state:: Done
state:: in progress
state:: in review
state:: on hold
state:: Pending
state:: Pushed to Prod
state:: Revision Needed
state::out-of-scope
suggestion
support
To Do
type :: Discussion
type :: Duplicate
type:: interaction-design
type:: New Feature
type::bug
type::documentation
type::incident
type::maintenance
type::question
type::recurring-tasks
vulnerability
Milestone
Clear milestone
No items
No milestone
Peerplays Improvements and Bugfixes 2024-01
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Peerplays_Blockchain/peerplays_migrated#844
No description provided.
Delete branch "feature/579-enable-hardfork-check"

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?