Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd a simpler way testing private tasks in step10 #140
Conversation
Private tasks can also be tested by just logging out. Keeping original guidance in place for additional insight.
apollo-cla
commented
Aug 29, 2017
|
@moberhuber: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/ |
CLAassistant
commented
Oct 7, 2019
•
|
Martin Oberhuber seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

moberhuber commentedAug 29, 2017
I'd like to suggest a simpler way testing private tasks, that I came across when working through the tutorial -- simply log out to make private tasks disappear: it's what I had intuitively tried, and wondered about before.
I'd still keep the original method in place as well, for additional insight, so the PR is just a small addition.