Create a new repository

I need a new repo to host the authentication microservice code for the Acme payments team. Create the repository under the AcmePayments organization named auth-service, initialize it with a README describing its purpose, add MIT license, and set default branch to main. Make the repo private and enable issues. Invite Priya Shah (priya@acme.com) with admin access and add a standard .gitignore for Go.

Before I hand this repo to the rest of the team, make it easy for someone to find the service intent and get started. Move the service description and run instructions to the top of the README, add a short example of how to build and run locally, expose the supported Go version, and surface the license and contribution guidelines. Flag any missing files reviewers expect: CONTRIBUTING.md, CODE_OF_CONDUCT.md, and a basic CI workflow.

We promised product a working repo for the auth microservice by Friday and I haven't created it yet. The team is blocked on starting integration tests. I'm worried about the private account settings and letting contractors see secrets. What likely will bite me if I rush this, and what's the safest minimal sequence to get a repo usable for the team without leaking credentials?

Over the last three projects I created new repositories that later caused delays because READMEs were thin, CI missing, or visibility wrong. I lose time fixing permissions and writing docs after people clone. What's the one checklist and habit I should adopt when creating a repo so the team can start work immediately and avoid rework?