Skip to content
This repository has been archived by the owner on Sep 19, 2024. It is now read-only.

Config command #891

Draft
wants to merge 352 commits into
base: development
Choose a base branch
from
Draft

Conversation

Keyrxng
Copy link
Member

@Keyrxng Keyrxng commented Nov 18, 2023

Resolves #888 & #887

Will cover E2E tests over the weekend

Quality Assurance:

0x4007 and others added 27 commits November 11, 2023 09:42
also changed time and priority labels from array of objects to array of strings
Copy link

netlify bot commented Nov 18, 2023

Deploy Preview for ubiquibot-staging failed.

Name Link
🔨 Latest commit a2ec9fa
🔍 Latest deploy log https://app.netlify.com/sites/ubiquibot-staging/deploys/6558b6a1e9e20c000896a100

@Keyrxng
Copy link
Member Author

Keyrxng commented Nov 18, 2023

@pavlovcik Forgive the noobness here but is this the best way to merge from your current refactor branch? Seeing all of those commits gives me the fear but I expect once merged it shouldn't make a difference or is this a disaster? 🤣

@0x4007
Copy link
Member

0x4007 commented Nov 20, 2023

I don't understand your question but technically speaking we don't have tasks open for contributors on this repository because of the anticipated complexities with merging. If you're particularly motivated to try even with this relatively adversarial merge environment (refactor is the top priority) then I would recommend you base your branch off of the latest, which actually is feat/contributor-incentives-total-scoring

For context, I'll try risky changes on a sub-branch, get them pretty stable, then merge to my main branch. In the context of the refactor, my "main branch" is refactor/general

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
4 participants