fix: query GitHub issue

[williamrusdyputra]

Resolves #287

Summary by CodeRabbit

• New Features

  • Improved handling of previous comments when issues are opened or edited, enhancing task management and error handling.
  • Updated comment retrieval to work with issues, providing better context and flexibility through a new categorization parameter.

• Bug Fixes

  • Enhanced consistency in comment retrieval functions to improve overall functionality.

[vercel[bot]]

@williamrusdyputra is attempting to deploy a commit to the Holdex Accelerator Team on Vercel.

To accomplish this, @williamrusdyputra needs to request access to the Team.

Afterwards, an owner of the Team is required to accept their membership request.

If you're already a member of the respective Vercel Team, make sure that your Personal Vercel Account is connected to your GitHub account.

[georgeciubotaru]

@williamrusdyputra try this on local trigger-dev with this PR

[georgeciubotaru]

@williamrusdyputra Also, please update your branch with main

[williamrusdyputra]

@georgeciubotaru alright, it should be "issue" not "issues", checked out from main also. Thank you!

[zolotokrylin]

@georgeciubotaru @williamrusdyputra, The title is vague. What exactly is the "issue"? Please keep it simple – be specific!

[georgeciubotaru]

@williamrusdyputra Did you check locally?

[williamrusdyputra]

@williamrusdyputra Did you check locally?

yeah, the graphql query error disappear. Now, it works like before, I just need a real testing example of holdex instead of the webhook example.

[georgeciubotaru]

@williamrusdyputra You can use this PR, parent issue with trigger-dev locally to check

[pr-time-tracker[bot]]

@zolotokrylin @georgeciubotaru ⚠️⚠️⚠️ You must submit the time spent on this PR. ⚠️⚠️⚠️

[coderabbitai[bot]]

Walkthrough

The recent updates enhance the management of comments in GitHub issues, specifically by refining the createJob function and comment retrieval methods. These changes modularize the handling of comments, improving organization, error management, and debugging capabilities. The code structure becomes clearer while preserving the intended functionalities, particularly by shifting focus from pull requests to issues.

Changes

Files	Change Summary
src/lib/server/trigger-dev/jobs/issues-creation.ts src/lib/server/trigger-dev/utils.ts	Improved createJob function to manage comments more effectively, switching comment retrieval from pull requests to issues, and adding a category parameter for enhanced flexibility.
src/lib/server/trigger-dev/jobs/index.ts	Modified integration configuration by removing the enabled: false property, which may allow integrations to be enabled by default.

Assessment against linked issues

Objective	Addressed	Explanation
Limit GitHub issues title to 65 characters maximum (#287)	❌	The objective of limiting the title length is not addressed in the code changes.

Poem

In the garden of code, hops a clever little sprite,
With comments now tidy, everything feels right.
No more pull requests, just issues in sight,
Organizing the chaos, making debugging a delight.
Oh, what a joy, as we code through the night! 🐇✨

---

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[williamrusdyputra]

Sent edited title with length exceeds 65

Now, the comment is gone after sending edited request with title less than 65.

[georgeciubotaru]

@williamrusdyputra I want to see these changes in Github meaning, you should change the title of the issue to have more than 65 then to change to a small one, and these changes should be reflected in Github

[williamrusdyputra]

let me reset one more time

[williamrusdyputra]

@georgeciubotaru I already tested in parent issue, the history is there, with this screenshot.