Migrate dyladan/component-owners

Open
#492 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
github, github-actions

Research direction

Start by comparing the workflows in dyladan/component-owners with the reusable workflows in this repository and identifying which dyladan/component-owners workflows should be replaced. Review the repository’s existing workflow documentation and usage examples before changing callers. The migration is done when dyladan/component-owners uses the shared workflows without retaining the single-maintainer dependency.

Written by the indexing model from the issue text.

Description

It will be great to migrate https://github.com/dyladan/component-owners
to shared-workflows.

Now, we have established good maintainers team. We can avoid bus-factor=1.

Dominant language
JavaScript
Stars
7
Forks
23
Avg merge
15h 46m
Merged PRs (30d)
41

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-telemetry/shared-workflows

All issues in open-telemetry/shared-workflows

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.