In the long term, we want to migrate all of our model computations to Research Cloud. Run a minimal version of the base model on VM2ĭocument necessary code changes to implement our updated code and potential bottlenecks.Run a minimal version of the base model on VM1.If an issue relates directly to one or more other issues, this should be stated in the description with a link to the other issue(s) (e.g., “Follow-up to #5”).įollowing #22, re-run the analysis on Research Cloud to see if that improves performance.It should include enough explanation and context that someone who is not intimately familiar with the other work going on at that moment can understand it clearly – remember that we will often be returning to these issues many months or even years later and trying to understand what was going on.The description should be precise enough that a third party can judge whether the issue was completed or not.Like the title, it should usually be written in imperative mode.Note that you can also change the title of an issue to make it more accurately reflect the current task. ![]() Using your time productively takes precedence over the priority ordering of tasks. You can work on open issues outside the current sprint if you have time left.Īll such rules are just a guideline. Issues are prioritized using the Project Board on GitHub. At this point, it can be split into separate issues, and the initial issue closed with an interim summary. For example, an issue that started with manageable scope may grow as the project expands or new questions arise. Usually, this means that an issue should not be more than a couple of weeks' worth of work and should not be open for more than a month or two. The creator chooses the assignee when the issue is created.Īn issue is a discrete, well-defined unit of work on a project. Getting Started with IssuesĮvery issue has a creator (i.e., the person who created it) and should have one or more assignees (the person(s) who will execute it). This building block aims to provide comprehensive guidance on the efficient use of GitHub Issues, teaching you how to write GitHub issues that get the job done! It begins with an introduction to GitHub Issues and subsequently delves into the best practices. They also help you keep track of what’s happening on projects and provide a durable, replicable record of the work for future reference. ![]() In combination with Kanban-style GitHub Project boards, they become a compelling way of coordinating teamwork. ![]() Github Issues can be used to clearly define tasks that either you or your team members will eventually work on. Want to change something or add new content? Click the Contribute button! Overview Visit our GitHub or LinkedIn page to join the Tilburg Science Hub community, or check out our contributors' Hall of Fame!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |