/fsc-evm

Home of EVM related macros, models and documentation

Primary LanguagePLSQLMIT LicenseMIT

README for EVM dbt macros, models and documentation

EVM Wiki & Documentation

Adding the fsc_evm dbt package

The fsc_evm dbt package is a centralized repository consisting of various dbt macros and snowflake functions that can be utilized across other repos.

  1. Navigate to packages.yml in your respective repo.
  2. Add the following (reference the latest version from here):
- git: https://github.com/FlipsideCrypto/fsc-evm.git
  revision: "v1.1.0"
  1. Run dbt clean && dbt deps to install the package

Troubleshooting: If package_lock.yml is present, you may need to remove it and re-run dbt deps. This is a known issue when installing dbt packages with the same version or revision tag.

Adding Release Versions

  1. Make the necessary changes to your code in your dbt package repository (e.g., fsc-utils).
  2. Commit your changes with git add . and git commit -m "Your commit message".
  3. Push your commits to the remote repository with git push ....
  4. Tag your commit with a version number using git tag -a v1.1.0 -m "version 1.1.0".
  5. Push your tags to the remote repository with git push origin --tags.
  6. Add official Release notes to the repo with the new tag.
  • Each Release should be formatted with the following template: 
    Release Title: <vx.y.z release title>
- Description of changes
- ...

**Full Changelog**: <link to the commits included in this new version> (hint: click the "Generate Release Notes" button on the release page to automatically generate this link)
  1. In the packages.yml file of your other dbt project, specify the new version of the package with:

Alternatively, you can use the makefile to create a new tag and push it to the remote repository:

make new_repo_tag

Last 3 tags:
v1.11.0
v1.10.0
v1.9.0

Enter new tag name (e.g., v1.1.0) or 'q' to quit:

vx.y.z # where x, y, and z are the new version numbers (or q to quit)

packages:


Regarding Semantic Versioning;
1. Semantic versioning is a versioning scheme for software that aims to convey meaning about the underlying changes with each new release.
2. It's typically formatted as MAJOR.MINOR.PATCH (e.g. v1.2.3), where:
- MAJOR version (first number) should increment when there are potential breaking or incompatible changes.
- MINOR version (second number) should increment when functionality or features are added in a backwards-compatible manner.
- PATCH version (third number) should increment when bug fixes are made without adding new features.
1. Semantic versioning helps package users understand the degree of changes in a new release, and decide when to adopt new versions. With dbt packages, when you tag a release with a semantic version, users can specify the exact version they want to use in their projects.

---

### DBT Resources:
- Learn more about dbt [in the docs](https://docs.getdbt.com/docs/introduction)
- Check out [Discourse](https://discourse.getdbt.com/) for commonly asked questions and answers
- Join the [chat](https://community.getdbt.com/) on Slack for live discussions and support
- Find [dbt events](https://events.getdbt.com) near you
- Check out [the blog](https://blog.getdbt.com/) for the latest news on dbt's development and best practices