feat: fetch the tags and push each one individually by WeslleyNasRocha · Pull Request #195

feat: fetch the tags and push each one individually by WeslleyNasRocha · Pull Request #195 · un-ts/changesets-gitlab

Walkthrough

This pull request adds a new changeset file that describes a minor feature for tag pushing and modifies the behavior of the publishing process. The changes update the evaluation of input flags using a centralized falsy values set, adjust the tag pushing control flow to allow individual tag pushes, and alter export declarations for several entities. Additionally, import statements and configuration details in workflows and package metadata have been updated.

Changes

File(s)	Change Summary
`.changeset/mighty-chefs-serve.md`	New changeset file added with metadata and a feature description for fetching and pushing tags based on package count and a feature flag.
`src/main.ts`, `src/utils.ts`	Updated `runPublish` to use `FALSY_VALUES` for evaluating `createGitlabReleases`; added new constants `FALSY_VALUES` and `GITLAB_MAX_TAGS`.
`src/run.ts`, `src/git-utils.ts`	Modified tag push control flow: introduced `pushAllTags` decision in `run.ts` and added an asynchronous `pushTag` function in `git-utils.ts`; updated export declarations.
`src/read-changeset-state.ts`	Replaced the workaround import with a direct import of `readChangesets` from `@changesets/read`.
`.github/workflows/pkg-pr-new.yml`, `package.json`	Updated workflow command with the `--compact` flag; revised the repository URL in `package.json`.

Sequence Diagram(s)

sequenceDiagram
    participant Runner as Publish Runner
    participant RunModule as run.ts
    participant GitUtils as git-utils.ts
    participant GitLab as GitLab Server

    Runner->>RunModule: runPublish(...)
    RunModule->>RunModule: Determine "pushAllTags" based on package count and feature flag
    alt pushAllTags is true
        RunModule->>GitUtils: pushTags(all tags)
    else pushAllTags is false
        RunModule->>GitUtils: For each package, call pushTag(tag)
    end
    GitUtils->>GitLab: Execute git push command(s)

Assessment against linked issues

Objective	Addressed	Explanation
Ensure all pipelines are triggered for each tag when more than 4 changesets are created (#194)	✅

Poem

In coding burrows, I hop with glee,
Tweaking tags where pipelines run free.
Each tag now hops on its own little trail,
No more lost pipelines in a four-tag tale.
Code-bunny smiles and twitches its ear — hooray! 🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

src/read-changeset-state.ts

Oops! Something went wrong! :(

ESLint: 9.23.0

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@1stg/eslint-config' imported from /eslint.config.js
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

src/git-utils.ts

Oops! Something went wrong! :(

ESLint: 9.23.0

src/utils.ts

Oops! Something went wrong! :(

ESLint: 9.23.0

2 others

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b681513 and e9ef014.

📒 Files selected for processing (8)

.changeset/mighty-chefs-serve.md (1 hunks)
.github/workflows/pkg-pr-new.yml (1 hunks)
package.json (1 hunks)
src/git-utils.ts (1 hunks)
src/main.ts (2 hunks)
src/read-changeset-state.ts (1 hunks)
src/run.ts (6 hunks)
src/utils.ts (1 hunks)

✨ Finishing Touches

📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @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 using 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 generate docstrings to generate docstrings for this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai plan to trigger planning for file edits and PR creation.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

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 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 for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

Walkthrough

Changes

Sequence Diagram(s)

Assessment against linked issues

Poem

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Documentation and Community

CodeRabbit Configuration File (`.coderabbit.yaml`)