-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change development prerequisites template #77
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,18 +2,24 @@ | |
Before you start working on the project, you need to get access to project-related items. | ||
|
||
Project manager can give you access to: | ||
* project in the project management software (productive, jira, etc) **LINK-TO-PROJECT** <!-- https://app.productive.io/path-to-project --> <!-- DEVELOPER --> | ||
* project Slack channels **LINK-TO-SLACK-CHANNELS** <!-- https://infinum.slack.com/path-to-project --> <!-- DEVELOPER --> | ||
* project Google Drive **LINK-TO-GOOGLE-DRIVE** <!-- https://drive.google.com//path-to-project --> <!-- DEVELOPER --> | ||
* project design (Figma, Sketch, etc) **LINK-TO-DESIGN** <!-- https://www.figma.com/path-to-project --> <!-- DEVELOPER --> | ||
|
||
* project in the project management software (productive, jira, etc) - [LINK-TO-PROJECT](LINK-TO-PROJECT) <!-- https://app.productive.io/path-to-project --> <!-- DEVELOPER --> | ||
* project Slack channels | ||
* [#internal-channel-name](LINK-TO-SLACK-CHANNEL) <!-- https://infinum.slack.com/path-to-project --> <!-- DEVELOPER --> | ||
* [#client-channel-name](LINK-TO-SLACK-CHANNEL) <!-- https://infinum.slack.com/path-to-project --> <!-- DEVELOPER --> | ||
* project Google Drive - [LINK-TO-GOOGLE-DRIVE](LINK-TO-GOOGLE-DRIVE) <!-- https://drive.google.com//path-to-project --> <!-- DEVELOPER --> | ||
* project design (Figma, Sketch, etc) - [LINK-TO-DESIGN](LINK-TO-DESIGN) <!-- https://www.figma.com/path-to-project --> <!-- DEVELOPER --> | ||
* 1password vault - VAULT-NAME <!-- Project ProjectName --> <!-- DEVELOPER --> | ||
|
||
Devops can give you access to: | ||
* 1password vault - **VAULT-NAME** <!-- DEVELOPER --> | ||
* git repository - **LINK-TO-GIT-REPO** <!-- https://github.com/path-to-project --> <!-- DEVELOPER --> | ||
* development and staging secrets - **LINK-TO-GIT-REPO** <!-- https://github.com/path-to-project --> <!-- DEVELOPER --> | ||
* bugsnag project - **LINK-TO-BUGSNAG** <!-- https://bugsnag.com/path-to-project --> <!-- DEVELOPER --> | ||
* semaphore project - **LINK-TO-SEMAPHORE** <!-- https://semaphoreci.com/path-to-project --> <!-- DEVELOPER --> | ||
* staging and/or UAT server | ||
|
||
* git repository - [LINK-TO-GIT-REPO](LINK-TO-GIT-REPO) <!-- https://github.com/path-to-project --> <!-- DEVELOPER --> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this can be given by a team lead or a github team maintainer |
||
* development and staging secrets - [LINK-TO-GIT-REPO](LINK-TO-GIT-REPO) <!-- https://github.com/path-to-project --> <!-- DEVELOPER --> | ||
* bugsnag project - [LINK-TO-BUGSNAG](LINK-TO-BUGSNAG) <!-- https://bugsnag.com/path-to-project --> <!-- DEVELOPER --> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. e a semahpre and bugsnag (and other 3rd party services) we have already listed in do we want to somehow reuse it or are we fine with duplicating? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, i saw that yesterday after i pushed this. I don't know actually 🤷♀️ Do you have a suggestion? I like that we have everything here in one place that's necessary for a developer to start to work on a project There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah, dont know either. coz mailgun is in that services but its access is solved via 1passowrd vault :D also should bugsnag and semaphore be something a team lead give access to? |
||
* semaphore project - [LINK-TO-SEMAPHORE](LINK-TO-SEMAPHORE) <!-- https://semaphoreci.com/path-to-project --> <!-- DEVELOPER --> | ||
* servers | ||
* staging - [LINK-TO-STAGING](LINK-TO-STAGING) | ||
* any other environment - [LINK-TO-OTHER-ENV](LINK-TO-OTHER-ENV) | ||
|
||
<!-- any other project specific services that are required for development --> | ||
|
||
# Type of tasks: | ||
|
@@ -94,4 +100,3 @@ Frontend / API | |
<architecture branch> -> <dashboard branch> | ||
[WriteCode] -> [Open PullRequest] -> (PR approved) -> <staging> -> [confirm](Qa approved) -> <master> -> [confirm](QA approved) | ||
``` | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add to codeowners as well? :)