modulatingforce/forcebot_rs
1
0
Fork 0
Code Issues 33 Pull requests 11 Projects 2 Activity

WIP: issue-routine-lock-idea1 #55

Draft
mzntori wants to merge 1 commit from issue-routine-lock-idea1 into issue-routine-lock
pull from: issue-routine-lock-idea1
merge into: modulatingforce:issue-routine-lock
Conversation 0 Commits 1 Files changed 1 +10 -25
mzntori commented 2024-04-01 14:21:44 -04:00
Collaborator
Copy link

Possible fix for #51.

Possible fix for #51.
mzntori added 27 commits 2024-04-01 14:21:44 -04:00
Merge branch 'main' into routines-functionality
All checks were successful
ci/woodpecker/pr/cargo-checks Pipeline was successful
Details
34c3c8af7a
(init) experiment test module
All checks were successful
ci/woodpecker/pr/cargo-checks Pipeline was successful
Details
4e9316ad49
(cont) routine start
All checks were successful
ci/woodpecker/pr/cargo-checks Pipeline was successful
Details
3f8e798050
(cont) start runonce
All checks were successful
ci/woodpecker/pr/cargo-checks Pipeline was successful
Details
b08d91af5d
proper join handling at custom
All checks were successful
ci/woodpecker/pr/cargo-checks Pipeline was successful
Details
8da8460e47
ISSUE - potential lock issue
All checks were successful
ci/woodpecker/pr/cargo-checks Pipeline was successful
Details
b5e95668a5
call loopbody on a read lock
All checks were successful
ci/woodpecker/pr/cargo-checks Pipeline was successful
Details
7db048937b
mzntori changed target branch from main to issue-routine-lock 2024-04-01 14:22:12 -04:00
modulatingforce added this to the Prototype 1.0 milestone 2024-04-02 09:48:44 -04:00
mzntori was assigned by modulatingforce 2024-04-02 09:48:52 -04:00
modulatingforce requested review from modulatingforce 2024-04-02 09:48:57 -04:00
modulatingforce added this to the Forcebot Prototype 1.0 Push project 2024-04-03 19:53:10 -04:00
All checks were successful
ci/woodpecker/pr/cargo-checks Pipeline was successful
Details
This pull request has changes conflicting with the target branch.
  • src/core/botmodules.rs
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin issue-routine-lock-idea1:issue-routine-lock-idea1
git checkout issue-routine-lock-idea1

Merge

Merge the changes and update on Forgejo.
git checkout issue-routine-lock
git merge --no-ff issue-routine-lock-idea1
git checkout issue-routine-lock
git merge --ff-only issue-routine-lock-idea1
git checkout issue-routine-lock-idea1
git rebase issue-routine-lock
git checkout issue-routine-lock
git merge --no-ff issue-routine-lock-idea1
git checkout issue-routine-lock
git merge --squash issue-routine-lock-idea1
git checkout issue-routine-lock
git merge --ff-only issue-routine-lock-idea1
git checkout issue-routine-lock
git merge issue-routine-lock-idea1
git push origin issue-routine-lock
Sign in to join this conversation.
Reviewers
No reviewers
modulatingforce
Labels
Clear labels   
Automated
  
Backlog
Post_Prototype_1.0

  
Bot_Code
Core

  
Bot_Code
Custom

  
CI/CD
  
Complexity
Advanced

  
Complexity
Basic

  
Complexity
Expert

  
Complexity
Intermediate

  
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Bug Fix

Branches intended to address an existing Bug

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Nix
  
Ownership
Collab

  
Ownership
Collab with Leads
Collab with one or more Leads

  
Ownership
Individual Lead

  
Ownership
In-Review
Ownership may be in a review or disputed status

  
Ownership
Needs Owner > May Delegate
Tasks that may need reassignment

  
Ownership
Workshop with Leads
Workshop Tasks

  
Phase 1.0
Requirements > Drafting

  
Phase 1.0
Requirements > Researching

  
Phase 1.0
Requirements > Review & Planning

  
Phase 2.0
Design > Research & Analysis

  
Phase 3.0
Coding > Implementation

  
Phase 4.0
QA > Unit Testing & Design

  
Phase 5.0
Resolution > Completed

  
Phase 5.0
Resolution > Review for Completion

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No labels
Automated
Backlog
Post_Prototype_1.0
Bot_Code
Core
Bot_Code
Custom
CI/CD
Complexity
Advanced
Complexity
Basic
Complexity
Expert
Complexity
Intermediate
Kind/Breaking
Kind/Bug
Kind/Bug Fix
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Nix
Ownership
Collab
Ownership
Collab with Leads
Ownership
Individual Lead
Ownership
In-Review
Ownership
Needs Owner > May Delegate
Ownership
Workshop with Leads
Phase 1.0
Requirements > Drafting
Phase 1.0
Requirements > Researching
Phase 1.0
Requirements > Review & Planning
Phase 2.0
Design > Research & Analysis
Phase 3.0
Coding > Implementation
Phase 4.0
QA > Unit Testing & Design
Phase 5.0
Resolution > Completed
Phase 5.0
Resolution > Review for Completion
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No milestone
Prototype 1.0
Projects
Clear projects
No items
No project
Forcebot Prototype 1.0 Push
Assignees
Clear assignees
No assignees
mzntori
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: modulatingforce/forcebot_rs#55
No description provided.
Delete branch "issue-routine-lock-idea1"

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?