feat: add git workflow

[sezeme]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @sezeme, I'm Gemini Code Assist¹! 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 introduces a new feature that establishes an automated workflow to integrate GitHub Pull Requests with Notion. It sets up a Node.js project with a TypeScript script that, when triggered by a PR event, extracts relevant information from the PR and uses the Notion API to update a corresponding entry in a Notion database. This aims to streamline the tracking and management of development tasks by linking them directly to GitHub PR activity.

Highlights

• Automated Notion Integration: Introduced a new TypeScript script (scripts/sync-notion.ts) designed to run as a GitHub Action, enabling automatic synchronization of GitHub Pull Request information with Notion database entries.
• PR-to-Notion Sync Logic: The core script extracts a document ID from the pull request's branch name (e.g., FEAT-123), queries a specified Notion database for a matching page, and then updates that page's 'GitHub Pull Requests' property with the PR's URL and its 'Status' property (e.g., '진행 중' for open, '완료' for merged) based on the PR's current state.
• Project Setup and Dependencies: Initialized a Node.js project with package.json, pnpm-lock.yaml, and tsconfig.json, setting up necessary dependencies like @actions/core, @actions/github, and @notionhq/client for interacting with GitHub Actions and the Notion API, along with tsx for running TypeScript directly.
• Updated Documentation: The README.md has been updated to include detailed setup instructions for both Notion (specifying the requirement for an 'ID' primary key) and GitHub secrets (explaining how to obtain and set the NOTION_DATABASE_ID).

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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. ↩

[gemini-code-assist]

Code Review

This pull request introduces a GitHub workflow to synchronize pull request status with a Notion database. Key areas for improvement include validating environment variables, using stable dependency versions, improving documentation, and enhancing type safety.

[gemini-code-assist]

The setup instructions should include setting NOTION_TOKEN as a repository secret, as the script requires it for Notion API authentication.

[gemini-code-assist]

Validate the presence of NOTION_TOKEN before initializing the notion client to prevent potential runtime errors if the environment variable is not set.

if (!process.env.NOTION_TOKEN) {
  throw new Error("NOTION_TOKEN is not set");
}
const notion = new Client({ auth: process.env.NOTION_TOKEN });

[gemini-code-assist]

Instead of using the non-null assertion operator (!), perform an explicit check for NOTION_DATABASE_ID to provide a more descriptive error message if it's not set.

const dbId = process.env.NOTION_DATABASE_ID;
if (!dbId) {
  throw new Error("NOTION_DATABASE_ID is not set");
}

[gemini-code-assist]

Consider adding the dist directory to .gitignore to prevent committing compiled build artifacts. This is a common practice to keep the repository clean.

# Node.js
node_modules/

# Build output
dist/

[gemini-code-assist]

The image assets/id.png is referenced but not included in the pull request. Ensure the image is added to the repository to avoid a broken link in the README.

[gemini-code-assist]

The @notionhq/client dependency is set to ^4.0.1, which may be an unstable version. Consider using the latest stable version to avoid potential issues.

    "@notionhq/client": "latest",

[gemini-code-assist]

Instead of using as any, rely on type inference by directly accessing the pull_request property from github.context.payload.

const pr = github.context.payload.pull_request;

[gemini-code-assist]

To improve type safety, define a specific type for the update object's properties instead of using any.

interface UpdateProps {
  [key: string]: { url?: string; select?: { name: string } };
}

const properties: UpdateProps = {
  [propPR]: {
    url: prUrl,
  },
};

if (prState) {
  properties[propStatus] = {
    select: { name: prState },
  };
}

await notion.pages.update({ page_id: pageId, properties });