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.

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

Issues are a pain --- what if we stubbed out branches instead? #33

Open
nathanallen opened this issue Mar 16, 2016 · 2 comments
Open

Issues are a pain --- what if we stubbed out branches instead? #33

nathanallen opened this issue Mar 16, 2016 · 2 comments

Comments

@nathanallen
Copy link
Contributor

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

@tgaff
Copy link
Member

tgaff commented Mar 17, 2016

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.

@tgaff
Copy link
Member

tgaff commented Mar 17, 2016

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants