assignees: ""

- OS: [e.g. iOS]

- Browser [e.g. chrome, safari]

- Version [e.g. 22]

Add any other context about the problem here.

assignees: ""

A clear and concise description of what the problem is. Example: I'm always frustrated when [...]

Add any other context or screenshots about the feature request here.

assignees: ""

- [ ] The PR conforms to DataHub's

[Contributing Guideline](https://github.com/linkedin/datahub/blob/master/docs/CONTRIBUTING.md) (particularly

[Commit Message Format](https://github.com/linkedin/datahub/blob/master/docs/CONTRIBUTING.md#commit-message-format))

name: check format

on:

push:

branches:

- master

pull_request:

branches:

- master

release:

types: [published, edited]

jobs:

build:

runs-on: ubuntu-latest

steps:

- uses: actions/checkout@v2

- name: Set up JDK 1.8

uses: actions/setup-java@v1

with:

java-version: 1.8

- name: Check format

run: ./gradlew spotlessCheck

- name: Slack failure notification

if: failure() && github.event_name == 'push'

uses: kpritam/slack-job-status-action@v1

with:

job-status: ${{ job.status }}

slack-bot-token: ${{ secrets.SLACK_BOT_TOKEN }}

channel: github-activities

[Documentation](#documentation) | [Roadmap](docs/roadmap.md) | [FAQ](docs/faq.md)

You should also visit [GMA Architecture](docs/architecture/architecture.md) to get a better understanding of how GMA is

implemented and [GMA Onboarding Guide](docs/how/entity-onboarding.md) to understand how to extend GMA for your own use

cases.

- [GMA Developer's Guide](docs/developers.md)

- [GMA Architecture](docs/architecture/architecture.md)

- [GMA Onboarding Guide](docs/how/entity-onboarding.md)

classpath 'com.diffplug.spotless:spotless-plugin-gradle:5.6.1'

classpath 'com.github.node-gradle:gradle-node-plugin:2.2.4'

classpath 'com.linkedin.pegasus:gradle-plugins:' + pegasusVersion

apply plugin: 'com.diffplug.spotless'

spotless {

// TODO Format Java

format 'md', {

target '**/*.md'

prettier().config([printWidth: 120, proseWrap: 'always'])

}

}

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making

participation in our project and our community a harassment-free experience for everyone, regardless of age, body size,

disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education,

socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

Examples of behavior that contributes to creating a positive environment include:

- Using welcoming and inclusive language

- Being respectful of differing viewpoints and experiences

- Gracefully accepting constructive criticism

- Focusing on what is best for the community

- Showing empathy towards other community members

- The use of sexualized language or imagery and unwelcome sexual attention or advances

- Trolling, insulting/derogatory comments, and personal or political attacks

- Public or private harassment

- Publishing others' private information, such as a physical or electronic address, without explicit permission

- Other conduct which could reasonably be considered inappropriate in a professional setting

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take

appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits,

issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any

contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the

project or its community. Examples of representing a project or community include using an official project e-mail

address, posting via an official social media account, or acting as an appointed representative at an online or offline

event. Representation of a project may be further defined and clarified by project maintainers.

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by direct messaging the project team

on [Slack]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and

appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter

of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent

repercussions as determined by other members of the project's leadership.

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at

[slack]: https://datahubspace.slack.com/join/shared_invite/zt-cl60ng6o-6odCh_I~ejZKE~a9GG30PA

For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq