Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: update styles for card component #2629

Closed
wants to merge 25 commits into from
Closed

Docs: update styles for card component #2629

wants to merge 25 commits into from

Conversation

leiyre
Copy link
Member

@leiyre leiyre commented Mar 31, 2023

Description

this PR updates styles for card component

Closes #2216

Type of change

  • Documentation update

Checklist

  • I have merged the original branch into my forked branch
  • I added relevant documentation
  • follows the style guidelines of this project
  • I did a self-review of my code
  • I made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

davidberenstein1957 and others added 25 commits March 22, 2023 09:47
# Description

The docker image description is updated on every docker image
publication. This PR changes this behavior to update it only when a
release event is triggered.

**Type of change**

(Please delete options that are not relevant. Remember to title the PR
according to the type of change)

- [x] Bug fix (non-breaking change which fixes an issue)

**How Has This Been Tested**

(Please describe the tests that you ran to verify your changes. And
ideally, reference `tests`)

Launching the ci pipeline.

**Checklist**

- [x] I have merged the original branch into my forked branch
- [ ] I added relevant documentation
- [x] follows the style guidelines of this project
- [x] I did a self-review of my code
- [ ] I made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have added relevant notes to the CHANGELOG.md file (See
https://keepachangelog.com/)

---------

Co-authored-by: Tom Aarsen <37621491+tomaarsen@users.noreply.github.com>
# Description

This PR adds a minimal setup for argilla deployment in a Kubernetes
cluster.


Closes #2144 


**Type of change**

(Please delete options that are not relevant. Remember to title the PR
according to the type of change)

- [ ] 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)
- [ ] Refactor (change restructuring the codebase without changing
functionality)
- [x] Improvement (change adding some improvement to an existing
functionality)
- [x] Documentation update

---------

Co-authored-by: david <david.m.berenstein@gmail.com>
# Description

This is the feature branch including all the changes related with new
database support.

---------

Co-authored-by: Francisco Aranda <francisco@recogn.ai>
Co-authored-by: frascuchon <francis@argilla.io>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: keithCuniah <keithcuniah@gmail.com>
Co-authored-by: Natalia Elvira <126158523+nataliaElv@users.noreply.github.com>
Co-authored-by: Daniel Vila Suero <daniel@recogn.ai>
Co-authored-by: David Berenstein <david.m.berenstein@gmail.com>
# Description

This PR changes how `copyright` docs attribute is set. Now instead of a
fix string we are getting dynamically the current year.

See
#2569 (comment)

**Type of change**

- [x] Improvement (change adding some improvement to an existing
functionality)

**How Has This Been Tested**
 
- [x] I have locally generated the documentation and I can see that the
copyright footer on the generated documentation is showing the current
year.

**Checklist**

- [x] I have merged the original branch into my forked branch.
- [x] I added relevant documentation
- [x] follows the style guidelines of this project
- [x] I did a self-review of my code
- [x] I made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] <del>I have added tests that prove my fix is effective or that my
feature works</del> Not necessary.
- [ ] <del>I have added relevant notes to the CHANGELOG.md file (See
https://keepachangelog.com/)</del> Not necessary.
# Description

This pull request aligns the image classification tutorial with the
correct implementation by displaying images from a URL on the front end.

- i.e. `_image_url` in metadata.
- install instructions are returned to standard.

Closes #2592 

**Type of change**

(Please delete options that are not relevant. Remember to title the PR
according to the type of change)

- [x] Bug fix (non-breaking change which fixes an issue)

**How Has This Been Tested**

The notebook has been run with a release v1.5.0 instance of Argilla.

**Checklist**
<!--pre-commit.ci start-->
updates:
- [github.com/charliermarsh/ruff-pre-commit: v0.0.254 →
v0.0.255](astral-sh/ruff-pre-commit@v0.0.254...v0.0.255)
<!--pre-commit.ci end-->

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
# Description
Main branch for front part of user settings

Please include a summary of the changes and the related issue. Please
also include relevant motivation and context. List any dependencies that
are required for this change.

Closes #2496 

**Type of change**

(Please delete options that are not relevant. Remember to title the PR
according to the type of change)

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Refactor (change restructuring the codebase without changing
functionality)
- [ ] Improvement (change adding some improvement to an existing
functionality)
- [ ] Documentation update

**How Has This Been Tested**

(Please describe the tests that you ran to verify your changes. And
ideally, reference `tests`)

- [ ] Test A
- [ ] Test B

**Checklist**

- [x] I have merged the original branch into my forked branch
- [ ] I added relevant documentation
- [x] follows the style guidelines of this project
- [x] I did a self-review of my code
- [ ] I made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [x] I have added relevant notes to the CHANGELOG.md file (See
https://keepachangelog.com/)

---------

Co-authored-by: keithCuniah <keithcuniah@gmail.comh>
Co-authored-by: José Francisco Calvo <josefranciscocalvo@gmail.com>
Co-authored-by: Francisco Aranda <francisco@recogn.ai>
Co-authored-by: José Francisco Calvo <jose@argilla.io>
Co-authored-by: frascuchon <francis@argilla.io>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: leire <leire@recogn.ai>
Co-authored-by: Natalia Elvira <126158523+nataliaElv@users.noreply.github.com>
Co-authored-by: Daniel Vila Suero <daniel@recogn.ai>
Co-authored-by: David Berenstein <david.m.berenstein@gmail.com>
Co-authored-by: leiyre <leire@argilla.io>
#2613)

# Description

This PR adds a missing step describing the execution of database
migrations for developer documentation.

Closes #2612

**Type of change**

(Please delete options that are not relevant. Remember to title the PR
according to the type of change)

- [ ] 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)
- [ ] Refactor (change restructuring the codebase without changing
functionality)
- [ ] Improvement (change adding some improvement to an existing
functionality)
- [x] Documentation update

**Checklist**

- [x] I have merged the original branch into my forked branch
- [x] I added relevant documentation
- [x] follows the style guidelines of this project
- [x] I did a self-review of my code
- [x] I made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] <del>I have added tests that prove my fix is effective or that my
feature works</del> (Not necessary)
- [ ] <del>I have added relevant notes to the CHANGELOG.md file (See
https://keepachangelog.com/)</del> (Not necessary)
# Description
Allow to access rule management while rule metrics are pending

Note: 
- this is not the most performant solution since the base-table
component is rerendered each time the input change
- there is a dirty fix (see RuleDefinition.vue) to ensure the reactivity
when the query search change. This correction close this issue #2561

Closes #2117 
Close #2561 

**Type of change**

(Please delete options that are not relevant. Remember to title the PR
according to the type of change)

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Refactor (change restructuring the codebase without changing
functionality)
- [ ] Improvement (change adding some improvement to an existing
functionality)
- [ ] Documentation update

**How Has This Been Tested**

(Please describe the tests that you ran to verify your changes. And
ideally, reference `tests`)

- [x] Textclassification

**Checklist**

- [x] I have merged the original branch into my forked branch
- [ ] I added relevant documentation
- [x] follows the style guidelines of this project
- [x] I did a self-review of my code
- [ ] I made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [x] I have added relevant notes to the CHANGELOG.md file (See
https://keepachangelog.com/)

---------

Co-authored-by: keithCuniah <keithcuniah@gmail.comh>
Co-authored-by: José Francisco Calvo <josefranciscocalvo@gmail.com>
Co-authored-by: Francisco Aranda <francisco@recogn.ai>
Co-authored-by: José Francisco Calvo <jose@argilla.io>
Co-authored-by: frascuchon <francis@argilla.io>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: leire <leire@recogn.ai>
Co-authored-by: Natalia Elvira <126158523+nataliaElv@users.noreply.github.com>
Co-authored-by: Daniel Vila Suero <daniel@recogn.ai>
Co-authored-by: David Berenstein <david.m.berenstein@gmail.com>
Co-authored-by: leiyre <leire@argilla.io>
Co-authored-by: Tom Aarsen <37621491+tomaarsen@users.noreply.github.com>
# Description

Just a minor fix on a broken link in the `README.md`.

**Type of change**

- [X] Documentation update
# Description

With this change, the new client is still compatible with an old server
version.

Ref [#2480](#2480)

**Type of change**

(Please delete options that are not relevant. Remember to title the PR
according to the type of change)

- [x] Bug fix (non-breaking change which fixes an issue)

**How Has This Been Tested**

(Please describe the tests that you ran to verify your changes. And
ideally, reference `tests`)

N/A

**Checklist**

- [x] I have merged the original branch into my forked branch
- [x] follows the style guidelines of this project
- [x] I did a self-review of my code
- [x] My changes generate no new warnings
- [x] I have added tests that prove my fix is effective or that my
feature works
@leiyre leiyre changed the base branch from develop to main March 31, 2023 12:20
@leiyre leiyre closed this Mar 31, 2023
@leiyre leiyre deleted the docs/style_card branch March 31, 2023 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

🍓 Review Tutorial cards style into docs
8 participants