11/19/2022 0 Comments Taskboard githubGoogle Sheets: habits that I haven’t completed yet today - Google Sheets API.Github Issues: non-PR issues that are assigned to me - GitHub API.TodoDock: tasks due in the next 2 days - TodoDock API.and let’s face it, who doesn’t like kanbans, am I right?.its API and webhooks make it very easy to build automation tools around it.A Trello board seemed to be the perfect place for this because: Long story short, a few weeks ago I decided to build a tool for periodically grabbing tasks from different sources and putting them in one place. This is just a subset of my daily habits :) I would have to give up on that if I used Trello for my habits. For instance, I like how Google Sheets allows me to visualize my daily habit progress in a grid. I didn’t want to stop using any of those tools, because each one does a great job in certain situations where others can be insufficient. It’s even worse when I’m on a mobile device because then I have to cycle through 5 different apps. On my computer, I literally have to keep 5 browser tabs open just so that I can see what’s on my to-do list at a given time and decide what to do next. Here are some of my favorite tools I use to manage different kinds of tasks: ToolĮven though I like the tools themselves individually, having to keep track of all of them at the same time is a pain in the ass, to be frank. I’m notoriously bad at remembering things, and my life would be a total mess if I didn’t somehow keep track of my personal tasks. To address this dilemma, I recently came up with a simple hack that lets me use all my favorite tools while interacting with just one. On the other hand, there’s no one-size-fits-all solution when it comes to task managers, so it makes sense to use the right tool for the job. We look forward to delivering even higher quality releases in 2020.Do you ever feel that the numerous productivity tools you use every day actually cost you more time than they are supposed to save? It sure doesn’t feel right when managing your tasks becomes a non-trivial task on its own. With our latest (and ongoing) efforts, the stability of our releases will be greatly improved. The goal has always been to release frequently with confidence. We have put a lot of work into our test suite, continuous integration and error monitoring tools for many years now. Any bug reports for our other products are still handled in our existing forum. Please note that the issues repo is just for our new pure JS component suite. Public issue trackerĪ great improvement with GitHub is that we now have a public support repo open for anyone who wants to submit a bug report or feature request. This is a massive improvement, and not just for us, but for anyone downloading our nightly builds. #Taskboard github code#This means that no untested or unreviewed code can enter our master branch. If tests pass, and if branch is not behind the master branch, GitHub will allow the branch to be merged. Once reviewed, GitHub triggers a test run to execute our test suite (powered by our Siesta testing tool). Instead all changes are manually reviewed by one of our senior “gatekeepers” using pull requests. It’s no longer possible for any of our developers to push code directly to our master/release branches. The most exciting part of our GitHub migration was to enable test results to block merge. This makes it so much easier to run tests for changes against all the affected code modules to assure a change in Grid does not break the Gantt. Previously we also had separate repos for each product, in GitHub we now use a single repo for all our pure JS components. But our needs for evergreen code meant we had to migrate to a more capable service. For source control, we have used Assembla for the past 10 years and it has served us well. The biggest change we made this fall was our migration to GitHub. We use services of great companies like Sauce Labs and BrowserStack for our cross browser testing. Having rapid test results is essential in a world where we don’t allow untested code to enter our repo. We also increased our test parallelization by adding more TC agents. It’s no secret that we are big fans of the JetBrains tool suite and we have now upgraded to the most recent TeamCity version. We estimate to be fully upgraded in time for the new year fireworks, meaning we can start 2020 by having our CI in great shape. This effort will greatly improve code stability as well as our code delivery efficiency. Additionally, it will also make our setup more transparent to our customers. This fall we decided to spend some time modernizing our continuous integration environment and tool chain.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |