'contributing' 검색 결과

Connect syncable entity components within Twenty server internals and expose them through GraphQL, an API query interface. It guides NestJS module registration, business services, response data conversion, and consistent handling of validation and execution errors.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Register builders, validators, and action handlers in NestJS modules
• Connect entity creation to validation and migration execution
• Expose entities through GraphQL with response data conversion

Implement caching and data conversion for syncable entities in Twenty's server code. Build lookup maps, convert stored records and inputs into flat representations, and resolve references to universal identifiers for later validation and processing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build a cache service for a new syncable entity
• Convert stored entities into flat data
• Transform creation and update inputs

Define the types and shared registrations needed to add a syncable entity to Twenty's server. Set up database entities, editable fields, action types, and relationships as the foundation for workspace migration implementation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Define a new syncable entity in Twenty
• Create flat data and migration action types
• Register editable fields and comparison rules

Guides contributors through adding a new programming language to Airflow, covering SDK structure, runtime coordination, communication rules, executable packaging, tests, and the documentation and configuration changes needed for a pull request.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding support for a new programming language
• Choosing how Airflow launches a language runtime
• Implementing communication and executable bundles

Helps contributors develop and fix Airflow’s Java SDK for JVM tasks. Explains public API boundaries, JAR packaging, Python coordination, communication schema updates, and the test commands used to validate changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding features or fixing bugs in the Java SDK
• Reviewing public API and internal implementation boundaries
• Investigating JAR discovery and JVM startup failures

Add a new exchange integration to CCXT using TypeScript and established exchange templates. Follow guidance for unified methods, data conversion, authentication, sandbox settings, recorded API test data, documentation, and checks across generated language implementations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add an exchange that CCXT does not yet support
• Convert exchange responses into CCXT's common data format
• Record real API responses for regression tests

Create a clear, concise README.md after reviewing the project and workspace. Uses example READMEs to guide structure and tone, formats the result for GitHub, and includes an existing project logo or icon when available.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Write a README for a project that lacks one
• Introduce a project to new readers
• Organize a README using existing examples

Guides a pull request from local checks through a recorded demo, GitHub upload, merge, and development environment verification. Explains the project's test and preview labels, attachment requirements, and rules for keeping the pull request current.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a pull request with local verification results
• Record and attach a demo of changed behavior
• Check when test and preview labels run workflows

Investigate incidents and recurring defects with structured methods such as Five Whys and Fishbone cause maps. Identify multiple contributing conditions, build a blame-free account of what happened, and propose practical changes to prevent similar failures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a production outage
• Investigate recurring defects
• Compare failing and working environments

Create GitHub pull requests with the gh command-line tool. Check linked issues, contributor permissions, branch conventions, and relevant tests, then prepare a title and description that follow the project's contribution rules.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Submit code changes for review
• Open a draft pull request
• Link a pull request to its issue

Turn a GitHub issue into a scoped implementation plan and, when authorized, code changes, tests, documentation, and a pull request that closes it. Check existing ownership and feedback to keep work aligned with acceptance criteria.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating an implementation plan from a GitHub issue
• Implementing an authorized issue with focused tests
• Updating documentation alongside behavior changes

Review recent Git commits to find changes that affect users, then update the relevant documentation pages. Identify missing pages, explain changed behavior or migration steps, and validate the resulting documentation with the project's build tools.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Update documentation after feature releases
• Check documentation gaps before a release
• Review changes since a specific tag

Investigate a specific OpenShell problem or feature need and create a structured GitHub issue. Record observed behavior, technical findings, alternatives, and missing evidence so a human can decide what to accept and pursue.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate an OpenShell bug and document reproduction steps
• Compare alternatives for a specific feature need
• Prepare a structured issue for human review

Implement an authorized fix for a reviewed security issue, check the plan against current code, and add regression tests to catch recurrence. Verify affected components and open a pull request that closes the issue while respecting disclosure rules.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing an approved security remediation plan
• Rechecking a reviewed fix against current code
• Adding regression tests for a security boundary

Prepare an open source contribution to Superset, from forking the code and setting up local development to running checks and opening a pull request. Follow repository rules and include evidence that the change works.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up a first contribution to Superset
• Preparing a pull request for a Superset bug fix
• Discussing a feature proposal before implementation

Prepare external contributions to gentle-ai through approved issues, accurate pull request descriptions, and plans for splitting large changes. Check claims against test results and GitHub state while respecting contributor and maintainer permissions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a contribution through the approved issue workflow
• Audit pull request claims against GitHub state
• Plan a sequence of related pull requests

Write and edit READMEs, guides, and other documentation using the code as evidence. Improve structure, wording, and terminology while checking related pages and links against the project's contribution process and documentation style guide.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing a guide for an existing feature
• Improving a README's structure and wording
• Updating documentation to match the implementation

When your CPA spikes, Claude breaks down exactly what caused it. It looks across your campaign data and isolates the contributing factors — audience fatigue, bid landscape shifts, creative decay, landing page conversion drops, budget distribution changes, or new competitor activity. Platform: Google and Meta.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write a blameless incident postmortem under postmortems/ following the Google SRE shape — evidence-based timeline, trigger vs root cause vs symptom, contributing factors, what went well, and owned+dated+verifiable action items. Read when asked to write a postmortem, do an incident review, run a root cause analysis, write up the outage, retro on the outage, or when the user says we had an incident and wants it documented. Do NOT read to frame a proposal (use frame-a-proposal), write a spec (use write-a-spec), record a decision (use record-a-decision), or review a design (use review-a-design) — a postmortem documents an incident that already happened, it does not propose, specify, decide, or critique future work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Modify, build, test, debug, and contribute to NVIDIA cuOpt (C++/CUDA, Python, server, CI). Use for solver internals, PRs, DCO, and code conventions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices. Triggers for both libraries and applications/CLIs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Draft and submit evidence-backed XQUIC GitHub bug issues in the repository's CONTRIBUTING and issue-template format. Use when preparing or opening an alibaba/xquic issue that must identify an exact RFC or draft mechanism, expected-versus-actual behavior, reproduction evidence, and optional verified source root cause; requires issue-check to return true before any GitHub submission.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SkillsBench task authoring — walk a contributor from idea to submission-ready task following CONTRIBUTING.md and the task-implementation rubric. Use when the user wants to create a new SkillsBench task, scaffold a task from an existing workflow (notebook, Excel workbook, document, dataset), convert a prompt or a benchmark item into a SkillsBench task, write skills for a task, or prepare a SkillsBench PR. Pairs with `task-review` (run that as a self-check before submitting).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Ships pull requests to open-source projects you don't maintain — CONTRIBUTING compliance, PR-size/scope checks, minimal-diff implementation, AI-disclosure PR descriptions, and rebase or bot-review replies. Use for 提 PR / 上游 PR / 贡献代码, "open a PR", "fix this upstream", "rebase against main", "respond to the bot review". Not for reviewing PRs as maintainer (use github-review-pr) or general GitHub CRUD (use github-ops).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.