search

ubiquity / ubiquibot

Putting the 'A' in 'DAO'
https://github.com/marketplace/ubiquibot
MIT License
16 stars 59 forks source link

Config command #891

Open Keyrxng opened 7 months ago

Keyrxng commented 7 months ago

Resolves #888 & #887

Will cover E2E tests over the weekend

Quality Assurance:

netlify[bot] commented 7 months ago

Deploy Preview for ubiquibot-staging failed.

Name Link
Latest commit a2ec9fafdeac13647fe398e392ef46892382124b
Latest deploy log https://app.netlify.com/sites/ubiquibot-staging/deploys/6558b6a1e9e20c000896a100
Keyrxng commented 7 months ago

@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 commented 7 months ago

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