Permalink
Switch branches/tags
1.12.1 1.17-beta CascadingDeleteLoopWhenCascadingFromBothSides DODocs DOManual ExecuteRaw GetStarted Legacy-Console-Projects ListImportBug MongoBackRelationBug MongoConnectionStringAgain MongoDBConnector MongoDBSelectionAndSSL MongoDeleteMany MongoDeleteProject MongoDeployBehavior MongoDoNotConnectNodesMoreThanOnce MongoDontTouchDataStructure MongoEmbeddedNestedTests MongoEmbeddedUpsert2 MongoEnableIDOnEmbeddedTypes MongoEnableMoreTests MongoFieldNameIndexError MongoFixInternalIDErrorAndTesting MongoJoinRelationsTowardsTopLevelShouldBeRemoved MongoObjectIds MongoRelationalFilters MongoRemoveEmbeddedDirectiveFromSchema MongoRemoveImportExportCapability MongoSSL MongoSSLOptional MongoTestingImprovements MongoUseSchemaInsteadOfProjectId NestedDeleteUpdateMany PrismaORMExamples RemoveNestedMutationsFromUpdateMany2 RemoveNodeInterfaceIfIDFieldNotNamedID RevertHiddenIdFieldChanges UpdateManyMutationInputType add-mysql8-to-test-pipeline alpha-with-empty-types-fix alpha beta cli-introspect cli-publish-flow client-strict-mode client-tests client-tests2 cluster-auth config-yml-description contributing db-docs delete-project deleting-link docs-1.16 docs-1.22 embedded endpoint etel_branch example-links examples-1.0 examples-deps examples-tests examplesAgain examplesRedux fix-2752 fix-2763 fix-2987 fix-3213 fix-3299 fix-3328 fix-client-typings fix-client fix/relay-connection fix/subscriptions fixOpenCode force-flag-cli generate generateTs graphql-database-circle graphql-database-client-api graphql-database-service-auth import improve-syntax-list-fields inflector-fixes js-update-many kubernetes-tutorial login-fix logout-command marktani-patch-1 marktani-patch-2 marktani-patch-3 marktani-patch-4 marktani-patch-5 marktani-patch-6 marktani-patch-7 marktani-patch-8 marktani-patch-9 master migration-guides mongo-data-model-validation mongo-introspect moreExamplesChanges native_image new-cli-beta new-cli new-readme playground-html prevent-deadlocks prisma-cli prisma_examples quickstart reference-docs remove-cloudwatch-metrics removeServerRegistry roadmap-and-architecture schemabuilder-perf-spec serverInfo sql-introspection tech-selector-for-getting-started tmp-db-introspect-refactoring tmp-fix-broken-gql-type tmp-introspection-fixes tmp-merge-schema-gen tmp-update-schema-gen-to-alpha-1.23 tmp-update-schema-gen-to-alpha update-contributing update-database-playground update-introspection-sdl update-playground update-schema-manager-endpoint updatePRISMA_MANAGEMENT_API_SECRET upgrade-guide upsert-mutaction version-check
Nothing to show
Find file Copy path
100 lines (59 sloc) 3.56 KB

Contribution Guidelines

Please read this guide if you're interested in contributing to Prisma.

We welcome any form of contribution, especially from new members of our community 💚

Discussions

Our community is a safe and friendly environment, where we support and treat each other with respect.

We invite you to actively participate in discussions on Github, the Forum and Slack.

You'll see many discussions about usage or design questions, but any topic is welcome. They are a great foundation to find potential issues, feature requests or documentation improvements.

Issues

To report a bug, you can use this template.

New bug reports require to be triaged. Oftentimes this includes creating a minimal reproduction, or verifying that the problem still occurs on the latest stable version or the unstable channel (see below).

When you're starting to look into fixing a bug, create a WIP PR that you mention in the original issue. This way, we ensure that everyone interested can share their thoughts, and duplicate work is prevented.

Adding tests is a great way to help preventing future bugs.

Documentation

You can either improve existing content or add new resources.

If you miss a particular information in the reference documentation, feel free to either create an issue or PR. We also welcome tutorials for related topics that you're interested in. If you come across an interesting pattern, feel free to add a new example to our example list!

Release Channels

Releases are separated into three channels: alpha, beta and stable. You can learn more about these three channels and Prisma's release process here.

Features

To request a new feature, you can use this template.

To contribute features or API changes, it's best to start a discussion in an issue first, ideally with a proposal. This allows everyone to participate and ensures that no potential implementation work is in vain.

Submitting Changes

After getting some feedback, push to your fork and submit a pull request. We may suggest some changes or improvements or alternatives, but for small changes your pull request should be accepted quickly.

Here are further contribution instructions:

For cli and server, PRs need to be made against the alpha branch (not master).

Logistics

Below are a series of steps to help you from a more "practical" perspective. If you need additional help concerning Git, Github has some great guides that you may want to check out! Check them out here

Fork the repo and then clone your fork

SSH:

git clone git@github.com:YOUR_USERNAME/prisma.git

HTTPS:

git clone https://github.com/YOUR_USERNAME/prisma.git

Add the remote upstream

git remote add upstream git://github.com/prisma/prisma.git

Fetch changes from upstream

git fetch upstream

Pull changes locally

git pull upstream master

Push changes up

git push

Labels

Read more about our labels here