From 6986da04da9423206f6d6804292b17b611881c5f Mon Sep 17 00:00:00 2001 From: Viren Nadkarni Date: Fri, 30 Jan 2026 15:11:13 +0530 Subject: [PATCH 1/2] Update repo metafiles --- CODEOWNERS | 1 + CONTRIBUTING.md | 40 +++------------------------------------- ISSUE_TEMPLATE.md | 34 ++-------------------------------- 3 files changed, 6 insertions(+), 69 deletions(-) create mode 100644 CODEOWNERS diff --git a/CODEOWNERS b/CODEOWNERS new file mode 100644 index 000000000000..43abb9be624b --- /dev/null +++ b/CODEOWNERS @@ -0,0 +1 @@ +* @viren-nadkarni diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b1701b6c1b45..8eda9240933f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,39 +1,5 @@ -# Table of Contents +If you find a bug within Moto, please contribute directly to the [Moto project](https://github.com/getmoto/moto). -- [Contributing code](#contributing-code) -- [Development Guide](#development-guide) - * [TLDR](#tldr) - * [Linting](#linting) -- [Maintainers](#maintainers) +If you find a bug in LocalStack or Moto-Ext, please report this to our [support team](https://docs.localstack.cloud/aws/getting-started/help-support/). -# Contributing code - -Moto has a [Code of Conduct](https://github.com/getmoto/moto/blob/master/CODE_OF_CONDUCT.md), you can expect to be treated with respect at all times when interacting with this project. - -# Development Guide -Please see our documentation for information on how to contribute: -https://docs.getmoto.org/en/latest/docs/contributing - -## TLDR - -Moto has a [Makefile](./Makefile) which has some helpful commands for getting set up. -You should be able to run `make init` to install the dependencies and then `make test` to run the tests. - -*NB. On first run, some tests might take a while to execute, especially the Lambda ones, because they may need to download a Docker image before they can execute.* - -## Linting - -Ensure that the correct version of ruff is installed (see `requirements-dev.txt`). Different versions of ruff will return different results. -Run `make lint` to verify whether your code confirms to the guidelines. -Use `make format` to automatically format your code, if it does not conform to `ruff`'s rules. - - -# Maintainers - -## Releasing a new version of Moto - -* Ensure the CHANGELOG document mentions the new release, and lists all significant changes. -* Go to the dedicated [Release Action](https://github.com/getmoto/moto/actions/workflows/release.yml) in our CI -* Click 'Run workflow' on the top right -* Provide the version you want to release -* That's it - everything else is automated. +Contributions to this codebase will be reviewed on a case-by-case basis to determine whether they are applicable to LocalStack. diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md index c3d7d3f655e8..771b6c29a55a 100644 --- a/ISSUE_TEMPLATE.md +++ b/ISSUE_TEMPLATE.md @@ -1,33 +1,3 @@ -## Reporting Bugs +This issue tracker is not actively monitored. -Please be aware of the following things when filing bug reports: - -1. Avoid raising duplicate issues. *Please* use the GitHub issue search feature - to check whether your bug report or feature request has been mentioned in - the past. -2. When filing bug reports about exceptions or tracebacks, please include the - *complete* traceback. Partial tracebacks, or just the exception text, are - not helpful. -3. Make sure you provide a suitable amount of information to work with. This - means you should provide: - - - Guidance on **how to reproduce the issue**. Ideally, this should be a - *small* code sample that can be run immediately by the maintainers. - Failing that, let us know what you're doing, how often it happens, what - environment you're using, etc. Be thorough: it prevents us needing to ask - further questions. - - Tell us **what you expected to happen**. When we run your example code, - what are we expecting to happen? What does "success" look like for your - code? - - Tell us **what actually happens**. It's not helpful for you to say "it - doesn't work" or "it fails". Tell us *how* it fails: do you get an - exception? A hang? How was the actual result different from your expected - result? - - Tell us **what version of Moto you're using**, and - **how you installed it**. Tell us whether you're using standalone server - mode or the Python mocks. If you are using the Python mocks, include the - version of boto/boto3/botocore. - - - If you do not provide all of these things, it will take us much longer to - fix your problem. +If you find a bug in LocalStack or Moto-Ext, please report this to our [support team](https://docs.localstack.cloud/aws/getting-started/help-support/). From 1de1c1dff91edfc1201fb0fc5ce00e3527c9a671 Mon Sep 17 00:00:00 2001 From: Viren Nadkarni Date: Tue, 3 Feb 2026 15:01:43 +0530 Subject: [PATCH 2/2] Update CODEOWNERS --- CODEOWNERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CODEOWNERS b/CODEOWNERS index 43abb9be624b..31bd92ae7048 100644 --- a/CODEOWNERS +++ b/CODEOWNERS @@ -1 +1,3 @@ * @viren-nadkarni + +**/models.py @localstack/phoenix