Capture the state of your space at a given point in time.
Unlike saving in other systems you may be used to, a commit does more than just capture the current state of your files. It also includes a reference to the commit that came immediately before it, enabling you to track your project's history.
Whenever you create or modify an asset, the changes are automatically added to a staging area in your browser's data store. Using the Git UI or terminal options in Y42, you can select staged changes and commit them into your space's Git repository.
It's important to write clear, concise commit messages to document the changes you've made. They're not only for you but for others who might work on the codebase now or in the future.
A good commit message should describe the nature and purpose of the change. Try to keep the commit message concise but be sure to include enough context for a reader to understand why the change is needed and what it does.
Good commit messages matter because they help others understand, learn, and contribute to your data pipeline codebase. Avoid vague messages like "fix bug", instead, you might say "fix off-by-one error in array iteration".
|Less desirable ❌
|fix data type mismatch in
customer_age field to handle negative values
|add data quality monitoring for
inventory.sql script for code readability
README with setup instructions
It's generally best to make commits in logical units. That is, each commit should be a self-contained change that fixes a specific bug or adds a specific feature. Avoid mixing different kinds of changes in a single commit, and try to commit frequently rather than waiting until you've made a large number of changes. Remember that the purpose of a commit is to document your changes, so commit whenever it makes sense to create a record of what you've done.