Development #63
Merged
Development #63
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `Mode` enum was added in this commit to handle different environment states. A new environment variable 'MODE' is now read and parsed, determining the active mode based on its value. This affects the `update_document_fields` function, which now receives the mode as an argument. The `create_custom_field` function has also been introduced to support field creation when running in 'create' mode. see #34
Refactored the process of creating custom fields to return a new custom field instead of returning an empty result. Custom field now is created from a key and string data type, instead of duplicating a field object. Error handling for custom field creation has been improved.
This commit introduces new package dependencies, including chrono and android related packages. It also updates the "CreateField" structure to use "Text" data type instead of "string", improving field creation and error handling in the Paperless module. Lastly, the visibility of the CreateField structure is changed to public. see #34
A new environment variable, MODE, has been added to the list of environments in the README file. This is an experimental feature that changes the mode of operation, allowing Doclytics to automatically create custom fields in Paperless.
…fields Feature/automatically create customfields
…56 The workflows for push, release, and production release have been updated to include a step to build the Docker image and push it to the GitHub Container Registry. The changes ensure the Docker images are not only pushed to DockerHub but also to GitHub's own container registry.
feat(deployment): add build and push to GitHub Container Registry see…
chore(deps): update rust docker tag to v1.79
This commit changes the repository owner name to lowercase when forming GitHub tags in the push, release, and release-prod workflows. The owner name was previously in its original case, which was resulting in inconsistency in GitHub tags.
# Conflicts: # .github/workflows/push.yml # .github/workflows/release-prod.yml # .github/workflows/release.yml
In the GitHub workflows (`push.yml`, `release.yml`, `release-prod.yml`), the method call to convert the GitHub repository owner name to lowercase was corrected from `lowercase` to `toLowerCase()`. This change will prevent potential errors in case the owner name contains upper case letters.
The actual repository owner was hardcoded as 'b-urb' for image tags in 'push.yml', 'release.yml' and 'release-prod.yml'. The repository owner part in the docker image tags should not be hardcoded, but we have to keep this for now to ensure workflow correctness.
This update adds a step to login to the GitHub Container Registry in the push, release, and release-prod workflow files. The Docker login action is used with `ghcr.io` as the registry and credentials provided by GitHub secrets.
The permissions for 'packages' and 'contents' have been added to the build-docker tasks in the push, release, and release-prod Github workflow files. This update allows these tasks to write packages and read contents, resulting in an improved and more secure continuous integration process.
feat(*): option to add language for base_prompt
chore(deps): update docker/build-push-action action to v6
|
🎉 This PR is included in version 1.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.