Skip to content

Update CHANGELOG.md#182

Merged
Dargon789 merged 1 commit into0xsequence-1.9.19from
Dargon789-patch-2
Jan 7, 2026
Merged

Update CHANGELOG.md#182
Dargon789 merged 1 commit into0xsequence-1.9.19from
Dargon789-patch-2

Conversation

@Dargon789
Copy link
Owner

@Dargon789 Dargon789 commented Jan 7, 2026

Summary by Sourcery

Documentation:

  • Remove stray merge conflict markers and metadata changelog entries from the indexer CHANGELOG to keep its history scoped correctly.

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@codesandbox
Copy link

codesandbox bot commented Jan 7, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@vercel
Copy link

vercel bot commented Jan 7, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
sequence.js Ready Ready Preview, Comment Jan 7, 2026 9:44am
wagmi-project Ready Ready Preview, Comment Jan 7, 2026 9:44am

@sourcery-ai
Copy link

sourcery-ai bot commented Jan 7, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Resolve merge conflict artifacts in the indexer service changelog by keeping the correct @0xsequence/indexer entries and removing stray metadata-related sections and conflict markers.

File-Level Changes

Change Details Files
Clean up merge conflict markers and incorrect section content in the indexer changelog.
  • Remove leftover Git merge conflict markers from the changelog header and version history sections.
  • Ensure the changelog header correctly refers only to @0xsequence/indexer.
  • Remove an unrelated @0xsequence/metadata 0.29.1 changelog entry that was accidentally introduced.
  • Keep the intended 0.29.3 indexer patch changes entry intact after conflict resolution.
packages/services/indexer/CHANGELOG.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@snyk-io
Copy link

snyk-io bot commented Jan 7, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@gemini-code-assist
Copy link

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on maintaining the integrity and accuracy of the project's changelog. It addresses and resolves merge conflicts that had inadvertently introduced incorrect or redundant entries into the CHANGELOG.md file for the @0xsequence/indexer package. The primary goal is to ensure that the changelog precisely reflects the version history and changes specific to the indexer service, providing a clear and clean record for future reference.

Highlights

  • Merge Conflict Resolution: This pull request resolves merge conflicts within the CHANGELOG.md file for the @0xsequence/indexer package.
  • Changelog Cleanup: Extraneous changelog entries related to the @0xsequence/metadata package, which were introduced during a merge conflict, have been removed, ensuring the indexer changelog is accurate.
  • File Integrity: The CHANGELOG.md file has been restored to a clean state, free of merge conflict markers and irrelevant entries.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request cleans up the CHANGELOG.md for the @0xsequence/indexer package by removing stray merge conflict markers and incorrectly merged entries from another package's changelog. The changes correctly resolve the formatting issues and ensure the changelog history is accurate for the indexer service. The modifications are sound and improve the readability and correctness of the documentation.

@Dargon789 Dargon789 merged commit 7a49258 into 0xsequence-1.9.19 Jan 7, 2026
18 of 21 checks passed
@Dargon789 Dargon789 deleted the Dargon789-patch-2 branch January 7, 2026 09:52
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.

1 participant