You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if we (mostly) only needed to look at Pull Requests to discuss/review them.
I suggest that instead of creating an issue, we can simply "stub" a branch by making a small change ( perhaps stubbing a folder with a .gitkeep file). That way our conversation all happens in one place.
This would be especially nice for homeworks and lectures.
In theory the Issue should be "planning" "idea" etc; that is, it's the ticket for this issue. And the PR should simply be code / typo review.
That's kindof the standard practice. Not sure if we can do that in practice or if it makes sense for us. It would be nice if they were a little more tightly integrated in github though.
We sorta also decided to use issues to discuss things that won't be merged here. For example I want to discuss the drill for next week with you, but it has it's own repo and will be linked directly from the schedule.
If I put the issue on it's repo then others probably won't see it unless I tag everyone.
Maybe a more global issue tracker is a better choice?
It would be nice if we (mostly) only needed to look at Pull Requests to discuss/review them.
I suggest that instead of creating an issue, we can simply "stub" a branch by making a small change ( perhaps stubbing a folder with a
.gitkeep
file). That way our conversation all happens in one place.This would be especially nice for homeworks and lectures.
@bgveenstra @tgaff @justincastilla @jlopker @cofauver
The text was updated successfully, but these errors were encountered: