Welcome to GitHub - Class 102 7/24/19

[nataliebradley]

Hey there :wave: Welcome to GitHub, we are excited you are here.

In effort to familiarize yourself with GitHub, we'd love for you to test out what you've learned so far and share your skills!

So while you're here, comment on this issue with the following:

• Say hello and @mention a coworker
• Create a checklist in markdown on ways you'll use GitHub in your day to day job
  • How to make a checklist
• Add something with BOLD text or italics
  • Styling text
• Sprinkle in some of your favorite emojis 🚀 👍
  • Using Emoji
• This isn't a test, there is no grading or judging, so Have fun with it! 🎉

Here are some links for the guides to help you along 👇

• Be Social
• Mastering Issues
• Mastering Markdown
• Mastering Documentation
• Learn about Project Boards

If you get stuck, feel free to @mention the GitHub team @department-of-veterans-affairs/github-experts

[froi]

Hi @elstudio! 👋

• [ ] track tasks with project boards
• [ ] discuss project things with my team using issues
• [ ] collaborate more with peer organizations

BTW, hello everybody 😄

[ghost]

Hello! Thank you for helping move the adoption of git and GitHub forward in the VA. I'm looking forward to leveraging the power of git, and the collaborative tools provided by GitHub, to create higher quality products.

Training Completed:

• [x] GitHub 101 👍
• [ ] GitHub 102 (Rescheduled)
• [ ] GitHub 103

$DAYJOB Uses

• [ ] Configure GitHub organization for my team.
• [ ] Move projects into GitHub
• [ ] Organize and manage source code and versions.
• [ ] Integrate documentation with source code.
• [ ] Leverage Issues, Projects, and automation to form consistent workflows for tracking changes to code and documentation.

[davissong]

Hello, this is great I am an SQA/SW Tester for EPMD. Loved the 1st training. I was not expecting to see how GitHub can be used for the new Agile SDLC, specifically how the 'work items' (tests-bugs) live with the User Stories they are testing. Looking forward to learning a lot more and implementing how SQA/SW Testers will use that part of GitHub...

I won't bother a coworker like I a marketing thing, lol [] get my GitHub access, this is a .com GitHub., so wondering if it is the right one. I expected a GitHub.va.gov.... [ ] waiting for the Thanksgiving project [ ] look for any TMS GitHub training for the project management, ie the 'issues' of type (i know this is a Rat term) in GitHub, not just the source code control of checking in and out
[ ] go thru the links above, 1st time I have seen this

I tried now, updated comment a few hours later

[jenhamm]

• [ ] Task 1
• [ ] Task 2 :bowtie:

[davissong]

Is this the place to ask what i hope are generic type questions, like: I see we have two GitHubs (GitHub.com and github.ec.com). The 'ec' one is called enterprise GitHub, but what is this one called? @nataliebradley

[nataliebradley]

@davissong Questions are always welcome!
The Department of Veterans Affairs has two instances of GitHub available to the community to advance development best practices — GitHub.com and GitHub Enterprise.

The default instance for all VA teams is GitHub.com. VistA projects will use the GitHub Enterprise (GitHub.va).

Here's some info on the differences:

GitHub.com (GitHub Enterprise Cloud)

This GitHub.com is the VA’s default source code repository. It is hosted by GitHub in their FedRAMP-authorized cloud environment. This instance provides the VA with access to thousands of open source repositories and code allowing for much more efficient software development and ease of new hire on-boarding. Access rights and permissions are granted by VA admins. Private repositories are configured by default within this instance and are only viewable and accessible to those granted permission by a VA Administrator. Public repositories within this instance are viewable as read-only to the general public. The GitHub.com instance is FedRamp tailored and has received VA ATO approval.

-This instance does support early Code Development and Project Management processes with vendors and contractors when conducting on-boarding operations.

• Supports integrations with cloud-hosted services like OMB’s Jira, CloudBees hosted Jenkins, and thousands of others available in the GitHub marketplace
• Repositories are private by default, but may be made public with approval of an organization owner -This instance supports VA open source obligation
• Integration with GitHub Enterprise is currently being implemented and tested.

GitHub.va (GitHub Enterprise Server)

GitHub.va (or GitHub Enterprise Server) is hosted behind the VA firewall. This instance should be used for VistA projects. Information hosted in this instance can only be accessed with VA PIV cards and its content can only be viewed internally. Private repositories within this instance are only viewable and accessible to those with appropriate access to the repository. Public repositories within this instance are viewable through read-only access to anyone within the VA network.

-This instance uses single sign-on (PIV) -This instance cannot be seen by individuals outside of the VA employee network.

All of this can be found on the OIT GitHub website: https://vaww.oit.va.gov/services/github Hope that helps!