Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Dev.MDD.Update instructions so that a Session must contain at least one commit #78

Open
CookingWithCale opened this issue May 28, 2022 · 0 comments
Open

Dev.MDD.Update instructions so that a Session must contain at least one commit #78

CookingWithCale opened this issue May 28, 2022 · 0 comments
Assignees
@CookingWithCale

Comments

@CookingWithCale
Copy link
Collaborator

CookingWithCale commented May 28, 2022 •
edited

A

Problem

The problem I am solving on this mission is that when we have no commits on a session I feel like it's demeaning and the extra issues can be viewed as pollution.

Solution

The solution to the problem is to minimize the log noise by making a Session one or more days. This way I don't have a lot of empty dev log entries.

Right now I find it helpful to create a session ticket for tomorrow, then update the time when I clock in, and eventually, I continuously integrate but right now it's just me.

File Affected
  1. ~/Dev/MDD/*

Hierarchy

Tags

Mission

Sessions

License

Copyright 2022 © Cale McCollough; all rights reserved.
@CookingWithCale CookingWithCale self-assigned this May 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CookingWithCale CookingWithCale

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CookingWithCale