run-llama/llama-hub
1
0
Fork 0
mirror of https://github.com/run-llama/llama-hub.git synced 2026-06-30 20:47:58 -04:00
Code Issues 96 Packages Projects Releases Wiki Activity

[PR #912] read all jira issues in chunks of 50 #915

New Issue
Open
opened 2026-02-15 18:16:51 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 18:16:51 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/run-llama/llama-hub/pull/912
Author: @ns-gsa
Created: 1/29/2024
Status: 🔄 Open

Base: main ← Head: jira_fetch_all

📝 Commits (4)

📊 Changes

2 files changed (+18 additions, -5 deletions)

View changed files

📝 llama_hub/jira/README.md (+5 -2)
📝 llama_hub/jira/base.py (+13 -3)

📄 Description

Description

  1. Read all tickets for the jira query in chunks of 50
  2. Add jira key to document description

Type of Change

Please delete options that are not relevant.

  • New Loader/Tool
  • Bug fix / Smaller change
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Added new unit/integration tests
  • Added new notebook (that tests end-to-end)
  • I stared at the code and made sure it makes sense

Suggested Checklist:

  • I have added a library.json file if a new loader/tool was added
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have 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
  • New and existing unit tests pass locally with my changes
  • I ran make format; make lint to appease the lint gods

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/run-llama/llama-hub/pull/912 **Author:** [@ns-gsa](https://github.com/ns-gsa) **Created:** 1/29/2024 **Status:** 🔄 Open **Base:** `main` ← **Head:** `jira_fetch_all` --- ### 📝 Commits (4) - [`c71bf6d`](https://github.com/run-llama/llama-hub/commit/c71bf6d6bebc6416f5144a00f6358a8ed96e950b) read all jira issues in chunks of 100 - [`5faccd5`](https://github.com/run-llama/llama-hub/commit/5faccd50f36b95daa2ba422484dcc1a4a0c44db3) Add issue key to document text - [`1b33842`](https://github.com/run-llama/llama-hub/commit/1b33842143cd50de8a37e4ada6258afdefa7cccc) run lint - [`fd2f802`](https://github.com/run-llama/llama-hub/commit/fd2f802999fc7a4ee3dbf81f77606423e3dd3432) Make max_results optional ### 📊 Changes **2 files changed** (+18 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `llama_hub/jira/README.md` (+5 -2) 📝 `llama_hub/jira/base.py` (+13 -3) </details> ### 📄 Description # Description 1. Read all tickets for the jira query in chunks of 50 2. Add jira key to document description ## Type of Change Please delete options that are not relevant. - [ ] New Loader/Tool - [x] Bug fix / Smaller change - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update # How Has This Been Tested? Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration - [ ] Added new unit/integration tests - [ ] Added new notebook (that tests end-to-end) - [x] I stared at the code and made sure it makes sense # Suggested Checklist: - [ ] I have added a library.json file if a new loader/tool was added - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have 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] New and existing unit tests pass locally with my changes - [x] I ran `make format; make lint` to appease the lint gods --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-15 18:16:51 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
good first issue
help wanted
idea
idea
idea
pull-request
Mirrored from GitHub Pull Request
 question
triage
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama-hub#915
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?