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
The "Issues" tab is a great way to setup to-do lists, identify problems, and assign tasks to team members. This is an example of one. I have assigned it to the three of you. You can use Markdown syntax or regular text. You can add links, lists, and other formatted content using
Setting Milestones
You can also use issues to set Milestones for your project. I am going to create a milestone to go along with this issue called "Commit team charter." I just wanted to show you how these tools work. Milestones can be a great way to pace your project. You might want to create milestones for "Finish document outline" or "commit first draft of document," or whatever else your team finds important
Keep in mind you don't have to use these features. The only requirements are that the team_docs and final documentation you create be written in Markdown and submitted to this repository. I'd encourage you to use these other features, though, as doc/code version control is an essential part of any technical communication job you might go into.
The text was updated successfully, but these errors were encountered:
Hi @umwrit350sp17/team-7
The "Issues" tab is a great way to setup to-do lists, identify problems, and assign tasks to team members. This is an example of one. I have assigned it to the three of you. You can use Markdown syntax or regular text. You can add links, lists, and other formatted content using
Setting Milestones
You can also use issues to set Milestones for your project. I am going to create a milestone to go along with this issue called "Commit team charter." I just wanted to show you how these tools work. Milestones can be a great way to pace your project. You might want to create milestones for "Finish document outline" or "commit first draft of document," or whatever else your team finds important
Keep in mind you don't have to use these features. The only requirements are that the team_docs and final documentation you create be written in Markdown and submitted to this repository. I'd encourage you to use these other features, though, as doc/code version control is an essential part of any technical communication job you might go into.
The text was updated successfully, but these errors were encountered: