.github/SUPPORT.md at main · GC-STEM/.github · GitHub
Skip to content

Latest commit

 

History

History
93 lines (69 loc) · 4.1 KB

SUPPORT.md

File metadata and controls

93 lines (69 loc) · 4.1 KB

Support

You are welcome to ask for help at any experience level. You do not need to solve the problem or know the right technical terms before contacting someone.

Use the support options listed in your course's Brightspace site. You can request course help without a GitHub account.

Table of Contents

  1. Choose a Support Channel
  2. Getting Started
  3. Protect Your Information
  4. Response Expectations
  5. Status

Choose a Support Channel

What you need Where to start
Help understanding coursework or assignment instructions Your instructor or the course's designated question forum in Brightspace
Questions about your grade, feedback, deadline, extension, or personal circumstances Contact your instructor privately using the method listed in Brightspace
Help with repository navigation, tools, or setup The affected repository's Discussions tab, if available, or your course's designated support channel
A correction to shared instructions, files, or links The affected repository's Issues tab, if available, or contact your instructor
Tutoring, academic coaching, or other learning support The support resources listed in Brightspace or mySNHU
An SNHU account or institutional technology problem IT Service Desk — SNHU sign-in required
An accessibility barrier or accommodation support Accessibility guidance
A suspected vulnerability, exposed password, or exposed private information Private security reporting
Harassment or another conduct concern Private conduct reporting

A GitHub Discussion is a conversation. An Issue is a report used to track a problem or suggested improvement.

If those features are unavailable, or you are unsure which channel to use, contact your instructor.

Getting Started

Review the relevant instructions and any matching questions or reports when practical. You do not need to complete every troubleshooting step before asking for help.

A brief description of what you were trying to do and where you became stuck is enough to start. Helpful details include:

  • The task, file, heading, or instruction involved
  • What happened and what you expected
  • An error message, copied as text when possible
  • Your operating system or application, if relevant
  • What you have already tried

Share only what you know. The person helping you can ask for more information.

If a problem prevents you from completing required coursework, contact your instructor promptly and explain which task is blocked. A GitHub report does not request or approve a deadline extension.

Protect Your Information

People outside SNHU can read public GitHub repositories. People with access to a private or internal repository can also read its shared conversations.

Use approved private course or institutional channels for grades, private feedback, student records, account details, and personal circumstances.

Before sharing files, screenshots, or logs, remove passwords, authentication codes, access tokens, personal information, and private communications. Follow course instructions when sharing assignment code, and do not post completed solutions to a support conversation.

Response Expectations

Use the response expectations published by your course or the support service you contact.

GitHub conversations may receive replies from students, faculty, staff, or repository maintainers. Maintainers are the people responsible for managing a repository. GitHub channels are not continuously monitored and do not guarantee a response time.

For a time-sensitive course problem, contact your instructor through the course's designated channel.

Status

This guidance is provisional while institutional review is pending. Current course instructions, SNHU policies, and applicable service terms continue to apply.