ProfessionalCommunity Edition

Submitting Bambdas to our GitHub repository

Last updated: February 13, 2025
Read time: 2 Minutes

When you write a Bambda, you can share it with the community. This collaboration enables the community to access an ever-growing library of Bambdas through our Bambdas repository on GitHub.

Before you submit

Before you contribute your Bambda, please make sure it meets our submission guidelines. The simplest way to make sure your Bambda includes the correct metadata is by exporting it directly from your Bambda library.

We also recommend that you run the Bambda Checker before submitting. The Bambda Checker is a Java tool that verifies Bambdas and generates README.md files before submission.

Submitting your Bambda

After you've confirmed your Bambda meets our guidelines, please follow these steps to submit it:

Export the Bambda file from your Bambda library. For instructions, see Managing Bambdas in your Bambda library - Exporting Bambdas.
Fork the Bambdas repository on GitHub then clone this fork to your local machine.
Create a new branch for your changes.
Place the exported .bambda file in the appropriate directory. The directory structure of the repo is broken down by Bambda type and tool. For example, a custom column Bambda for Logger would be placed in the Custom Columns > Logger directory.
Make any necessary changes.
Push the changes to your fork.
Open a pull request. Make sure to include a concise description of your Bambda in the request.

Review and merge

Your submission will be reviewed by both the community and our team. We encourage you to actively and constructively engage with any feedback received during this process.

If your submission includes multiple Bambdas, you may be asked to split it into multiple pull requests. This could happen if some Bambdas require further feedback, while others are ready to merge.