Skip to content

Latest commit

 

History

History
145 lines (94 loc) · 5.49 KB

File metadata and controls

145 lines (94 loc) · 5.49 KB

🤝 Contribution Guidelines

First of all, thank you for taking the time to contribute! We truly appreciate every contribution.

We welcome all contributions. Whether you're fixing typos, adding new resources, or suggesting improvements - it's all valuable!

To contribute, you'll need a GitHub account

How GitHub Contributor Recognition Works:

  • GitHub's system automatically tracks contributors via Pull Requests
  • To appear in the repository's Contributors list, you need to submit a PR
  • Simple suggestions via Issues don't trigger automatic recognition

Don't worry - it's not difficult! We've created a visual guide below to help.

While you can always just suggest resources via Issues and we'll add them, we welcome you to become an officially recognized contributor!

How to Contribute

Option 1 (Suggest via Issue)

You can either open a new issue or comment in our permanently open suggestions issue - whichever is more convenient for you.

Add to Open Issue

  • Add your suggestion here

Create New Issue

  • Open new issue here

Option 2 (Become a Contributor via Fork and Pull Request)

Starting from this repository's main page: awesome-data-analysis

  1. Click the pencil (✏️) icon to edit the README.md file
step1
  1. Create your fork:
    • GitHub will prompt you to create a fork
    • Click the green "Fork this repository" button
step2
  1. Add your resource:
    • Navigate to the relevant section in the file
    • Add your resource using this format:
      - [Resource Name](URL) - Brief description.
    • Example:
      - [Awesome Data Science](https://github.com/academic/awesome-datascience) - A curated list of courses, books, tools, and resources for data science.
    • Use the Preview tab (at the top) to check how your contribution will look
step3
  • Please avoid unnecessary formatting - this simplifies the review process
  1. Propose the changes:
    • In the top section of the page, click the green "Commit changes" button
step4
  • In the "Propose changes" dialog:
    • Commit message: Briefly describe your change
    • Extended description (optional): Add more details if needed
  • The exact content isn't critical - this just helps understand the Pull Request better
  • Click the green "Propose changes" button
step5
  1. Create a Pull Request:
    • Optional: Review your changes in the lower part of the screen:
      • Green: Lines you added or modified
      • Red: Original content before changes
    • If everything looks correct, click "Create Pull Request"
step6
  • The description will be pre-filled with your commit message - you can keep it as is or modify it
  • Click "Create Pull Request" again to finalize
step7

That's it! Once your PR is merged, you'll appear in our contributor list.

About your fork after contributing:

  • You can safely delete the fork anytime from your repository settings
  • Go to Your Fork Repo → Settings → Scroll Down to Danger Zone → Click "Delete this repository"
  • This won't affect the main project or your contributor status
  • We'd be happy if you keep Your Fork Repo for future contributions
  • You can always create a new fork later if needed

Option 3 (For local editing)

  1. Clone the repo:

    git clone https://github.com/PavelGrigoryevDS/awesome-data-analysis
  2. Create a branch, make changes, and push

Submission Format

For resource suggestions, please use this format:

- [Resource Name](URL) - Brief description.

Quick Tips

  • One resource per PR
  • Check for duplicates first
  • Keep descriptions short and factual
  • Test all links before submitting

Quality Standards

Resources should be:

  • High quality
  • Useful for the majority of data analysts/scientists
  • Free or have a substantial free tier

Category Organization

  • Add resources to existing categories when possible
  • New categories must be broadly useful
  • Avoid overly specific categories
  • Maintain consistent section structure

Review Process

  • PRs will be reviewed within 1-3 days
  • We may suggest improvements before merging

Thank you for helping improve this awesome list!