Skip to content

Conversation

Innixma
Copy link
Contributor

@Innixma Innixma commented Jan 15, 2025

Issue #, if available:

Description of changes:

  • Update CONTRIBUTING.md to be up to date and provide additional useful information

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@Innixma Innixma added this to the 1.3 Release milestone Jan 15, 2025
@Innixma Innixma requested a review from shchur January 15, 2025 00:47
Copy link

Job PR-4798-a7dfb58 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-4798/a7dfb58/index.html

Copy link
Collaborator

@shchur shchur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few comments but otherwise LGTM

CONTRIBUTING.md Outdated

To send us a pull request, please:

1. Fork the repository.
1. Fork the repository and clone the source code to your local machine.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add pointers to the official GitHub docs on forking & cloning?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great idea, added

CONTRIBUTING.md Outdated

To send us a pull request, please:

1. Fork the repository.
1. Fork the repository and clone the source code to your local machine.
2. Modify the source (see details below); please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
3. Ensure local tests pass.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have an example showing which tests need to pass?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed reference to tests since it would take too long for them to run

CONTRIBUTING.md Outdated
2. Modify the source (see details below); please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
3. Ensure local tests pass.
4. Commit to your fork using clear commit messages.
5. Send us a pull request, answering any default questions in the pull request interface.
6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
7. To spin up the platform tests, which test autogluon among macos and windows, comment on the PR with `/platform_tests`(You would need write permission to AutoGluon repo). It is recommended to run the platform tests only after you have passed the default CI.
7. (Optional) To spin up the platform tests, which test autogluon among MacOS and Windows, comment on the PR with `/platform_tests`(You would need write permission to AutoGluon repo). It is recommended to run the platform tests only after you have passed the default CI and only for changes that are likely to cause platform specific issues.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIRC, one can only start platform tests from a branch of the autogluon/autogluon repo and not for branches of the forks. It makes sense for us (maintainers) to be aware of this, but probably not something for the users to worry about since they cannot run the tests.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, moved to a different section focusing on maintainer specific contribution instructions

CONTRIBUTING.md Outdated
@@ -69,10 +70,51 @@ cd ../multimodal/
pytest
cd ../timeseries/
pytest
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lines 61-72 could be replaced with

pytest common/tests
pytest core/tests
...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice, updated

CONTRIBUTING.md Outdated
Comment on lines 78 to 94
# the below will check for changes that will occur if performing linting

# black
ruff format --diff "timeseries/"
# isort
ruff check --select I "timeseries/"

# black
ruff format --diff "common/"
# isort
ruff check --select I "common/"

# black
ruff format --diff "features/"
# isort
ruff check --select I "features/"
```
Copy link
Collaborator

@shchur shchur Jan 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe the following is shorter / more readable?

# Check formatting and the order of imports
for dir in "timeseries" "common" "features"; do
  ruff format --diff $dir
  ruff check --select I $dir
done

These checks don't technically perform linting, only style checks (formatting and import sorting). Linting would be done with ruff check $dir and that's only enabled for timeseries (equivalent to flake8).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point, updated and changed wording

CONTRIBUTING.md Outdated
Comment on lines 97 to 114
# the below will actively change files to satisfy linting
# DO NOT run the below commands before running the above commands, as you risk introducing many unintended changes.

# black
ruff format "timeseries/"
# isort
ruff check --fix --select I "timeseries/"

# black
ruff format "common/"
# isort
ruff check --fix --select I "common/"

# black
ruff format "features/"
# isort
ruff check --fix --select I "features/"
```
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

for dir in "timeseries" "common" "features"; do
  ruff format $dir
  ruff check --fix --select I $dir
done

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated thanks

CONTRIBUTING.md Outdated

- After you open your pull request, our CI system will run for little while to check your code and report found errors. Please check back and fix any errors encountered at this stage (you can retrigger a new CI check by pushing updated code to the same PR in a new commit).

- We also encourage you to contribute new tutorials or example scripts using AutoGluon for applications you think other users will be interested in. Please see [`docs/tutorials/`](https://github.com/autogluon/autogluon/tree/master/docs/tutorials) or [`examples/`](https://github.com/autogluon/autogluon/tree/master/examples). All tutorials should be Jupyter notebooks (.ipynb) files.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Side note: Is our examples folder up-to-date / maintained?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

almost certainly not, will remove the mention here.


- After you open your pull request, our CI system will run to check your code and report found errors. This may take a few hours. Please check back and fix any errors encountered at this stage (you can retrigger a new CI check by pushing updated code to the same PR in a new commit).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The maintainers would need to approve the CI run first.

CONTRIBUTING.md Outdated
```

- Lint the code, so it adheres to our code style by running the below command. Note that our lint check for tabular, core, and multimodal modules are temporarily disabled.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we enable linting & style checks for these modules now that we are done with v1.2.0?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I plan to soonish, once some of the old PRs are merged (working on it)

Innixma and others added 2 commits January 15, 2025 10:47
Co-authored-by: Oleksandr Shchur <oleks.shchur@gmail.com>
@Innixma Innixma merged commit 4179ea2 into autogluon:master Jan 15, 2025
2 checks passed
Copy link

Job PR-4798-6c9071c is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-4798/6c9071c/index.html

@Innixma Innixma deleted the update_contrib branch April 16, 2025 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants