minor df cleanup #1

Merged
finn merged 1 commits from dfcleanup into master 2024-07-07 22:05:28 +00:00
Owner

Creating a Pull Request

We use github actions to do automatic semantic versioning, so please use the following nomenclature for the commit message according to the type of change:

  • Prefix with feat:, and it will trigger a minor version bump.
  • Prefix with fix:, and it will trigger a patch version bump.
  • Prefix with BREAKING CHANGE:, and it will trigger a major version bump.

Description of the change

Motivation and Context

How Has This Been Tested?

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation (adding or updating documentation)

Checklist:

  • My change requires a change to the documentation and I have updated the documentation accordingly.
  • My change adds a new configuration variable and I have updated the .env.example file accordingly.

And lastly, many thanks for taking your time to help us improve this project !

<!-- BEFORE SUBMITTING YOUR PR, PLEASE REMOVE THIS TEXT --> <!-- REMOVE START --> # Creating a Pull Request We use github actions to do automatic [semantic versioning](https://github.com/semantic-release/semantic-release), so please use the following nomenclature for the commit message according to the type of change: * Prefix with `feat:`, and it will trigger a minor version bump. * Prefix with `fix:`, and it will trigger a patch version bump. * Prefix with `BREAKING CHANGE:`, and it will trigger a major version bump. <!-- REMOVE END --> ## Description of the change <!--Please be very clear on the intention of the modifications included in the pull request.--> <!--If it is a bug, explain what is the issue at hand and how you are fixing it. --> <!--If it is an improvement, explain why do you think it is needed and the benefits it brings to the project. --> <!--Ideally I would recommend to create an issue first to discuss the new feature with the developers.--> ## Motivation and Context <!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. --> ## How Has This Been Tested? <!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, tests ran to see how --> ## Types of Changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [x] Documentation (adding or updating documentation) ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] My change requires a change to the documentation and I have updated the documentation accordingly. - [ ] My change adds a new configuration variable and I have updated the `.env.example` file accordingly. And lastly, many thanks for taking your time to help us improve this project !
finn added 1 commit 2024-07-07 22:04:56 +00:00
minor df cleanup
Some checks failed
Test / build (pull_request) Has been cancelled
87bde44854
finn merged commit 668026282e into master 2024-07-07 22:05:28 +00:00
finn deleted branch dfcleanup 2024-07-07 22:05:38 +00:00
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: finn/pmb-pf#1
No description provided.