-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config command #891
base: development
Are you sure you want to change the base?
Config command #891
Conversation
…lefoo/ubiquibot into ubiquity-whilefoo-refactor/bot-config
…butor-incentives-total-scoring
also changed time and priority labels from array of objects to array of strings
… top via return etc
…es-total-scoring-duplicate-fix
❌ Deploy Preview for ubiquibot-staging failed.
|
@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? 🤣 |
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 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 |
Resolves #888 & #887
Will cover E2E tests over the weekend
Quality Assurance: