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

Bot admins in env file #22

Merged
modulatingforce merged 7 commits from haru_test into master 2024-04-09 13:48:55 -04:00
Conversation 4 Commits 7 Files changed 2 +12 -3
HaruYuumei commented 2024-03-17 17:23:00 -04:00
Collaborator
Copy link
No description provided.
HaruYuumei added 1 commit 2024-03-17 17:40:23 -04:00
HaruYuumei added 1 commit 2024-03-17 18:12:44 -04:00
bot admins change
Some checks failed
ci/woodpecker/pr/cargo-checks Pipeline failed
Details
5fb373c522
modulatingforce commented 2024-03-17 18:18:06 -04:00
Owner
Copy link

So units tests failed FUCK - I will have to look into that separately

So units tests failed FUCK - I will have to look into that separately
HaruYuumei changed title from WIP: Haru test to WIP: Bot admins in env file 2024-03-17 18:21:43 -04:00
modulatingforce added 1 commit 2024-03-17 19:29:29 -04:00
adj adminvector()
All checks were successful
ci/woodpecker/pr/cargo-checks Pipeline was successful
Details
f7881fa07d
modulatingforce added a new dependency 2024-03-17 20:12:01 -04:00
#20 [ENH] `BotAdmins` can be defined in `.env`
modulatingforce removed a dependency 2024-03-17 20:41:46 -04:00
#20 [ENH] `BotAdmins` can be defined in `.env`
modulatingforce added a new dependency 2024-03-17 20:42:08 -04:00
#20 [ENH] `BotAdmins` can be defined in `.env`
modulatingforce added the
Bot_Code
Core
 label 2024-03-27 17:48:26 -04:00
modulatingforce added the
Kind/Enhancement
Complexity
Basic
Priority
Low
 labels 2024-03-27 18:23:57 -04:00
modulatingforce added this to the Forcebot Prototype 1.0 Push project 2024-03-27 18:47:32 -04:00
modulatingforce commented 2024-03-27 20:21:12 -04:00
Owner
Copy link

I believe we left off here with the following that I had planned to demonstration using git and the forge

Plan of Action

  • Creating a new Branch
  • Using PR to Collaborate on a Branch
  • Collaborate by having someone Code a Simple Change to the PR
  • Collaborate by having someone create Unit Tests for the added Change
  • Approving a Merge with the group
I believe we left off here with the following that I had planned to demonstration using git and the forge # Plan of Action - [x] Creating a new Branch - [x] Using PR to Collaborate on a Branch - [ ] ~~Collaborate by having someone Code a Simple Change to the PR~~ - [ ] ~~Collaborate by having someone create Unit Tests for the added Change~~ - [ ] ~~Approving a Merge with the group~~
modulatingforce added the
Phase 3.0
Coding > Implementation
 label 2024-03-27 20:21:28 -04:00
HaruYuumei was assigned by modulatingforce 2024-03-31 09:59:48 -04:00
modulatingforce added the
Ownership
Individual Lead
 label 2024-03-31 09:59:59 -04:00
modulatingforce self-assigned this 2024-04-09 11:37:37 -04:00
modulatingforce commented 2024-04-09 11:41:18 -04:00
Owner
Copy link

No need for unit tests - the change isn't requiring complex business logic.

I'll review this one last time before approving

No need for unit tests - the change isn't requiring complex business logic. I'll review this one last time before approving
modulatingforce requested review from modulatingforce 2024-04-09 11:41:26 -04:00
modulatingforce added 1 commit 2024-04-09 12:51:58 -04:00
modulatingforce commented 2024-04-09 12:52:16 -04:00
Owner
Copy link

Looking good. Approving

Looking good. Approving
modulatingforce added 1 commit 2024-04-09 12:56:29 -04:00
modulatingforce added 1 commit 2024-04-09 13:39:59 -04:00
Merge branch 'master' into haru_test
Some checks failed
ci/woodpecker/pr/cargo-checks Pipeline failed
Details
b949c70fa8
modulatingforce added 1 commit 2024-04-09 13:47:10 -04:00
clippy
All checks were successful
ci/woodpecker/pr/cargo-checks Pipeline was successful
Details
7f49693a94
modulatingforce changed title from WIP: Bot admins in env file to Bot admins in env file 2024-04-09 13:48:36 -04:00
modulatingforce merged commit b8c33d2339 into master 2024-04-09 13:48:55 -04:00
modulatingforce deleted branch haru_test 2024-04-09 13:48:55 -04:00
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
Projects
Clear projects
No items
No project
Forcebot Prototype 1.0 Push
Assignees
Clear assignees
No assignees
modulatingforce
HaruYuumei
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#20 [ENH] `BotAdmins` can be defined in `.env`
modulatingforce/forcebot_rs
Reference: modulatingforce/forcebot_rs#22
No description provided.
Delete branch "haru_test"

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?