Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Set up Felt Chatbot development branch and prerelease workflow

Abierto
  • ¿Algo no está bien?
#918 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
git, github-actions, typescript
Área
build-system, ci-cd, release

Línea de trabajo

Start with packages/module/release.config.js, packages/module/package.json, and the .github/workflows Check-pr.yml and release.yml files, then review the existing branch and tag setup. Done means the felt-v1 branch and prerelease stream are configured, the agreed package name and prerelease tag are set, workflows run for the branch, and CI and NPM show the expected prerelease versions.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

  • Treat Chatbot as the first Felt extension.

  • Create/configure its felt-v1 branch and prerelease stream.

  • Update package name in package.json to match the @felt/felt-chatbot or whatever pkg name team agrees on. It should publish to NPM in this space.

“How to” docs modified from

To set up and release prereleases for extensions

  1. Create a new branch to be the home of your previous version:
  2. Branch off of your main branch with the name being the current version number
  3. Push that branch to your remote
  4. Change branches back to main
  5. If it doesn’t already exist: Create a git tag from the latest commit on the main branch with a name of prerelease-v${previous version number}
  6. i.e. prerelease-v${6}
  7. In the new major release branch: update packages/module/release.config.js:
  8. Edits to the branches array:
  9. Add a new object for your new major release branch
  10. ​​{ name: '<branch-name>', channel: 'prerelease', prerelease: 'prerelease' }
  11. (optional) add a dryRun: true 
  12. This is recommended because it helps to prevent accidentally releasing a version that you don’t mean to
  13. Update ./github/workflows
  14. Edit the Check-pr.yml branches entry to include the branch name you used in step 1
  15. Edit the release.yml branches entry to include the branch name you used in step 1
  16. Check for any other workflows that fire for events on the main branch and edit the branches key as above
  17. Update packages/module/package.json
  18. Update the publishConfigs to have tags: ‘prerelease’
  19. Commit and push/PR changes
  20. (optional) create a new branch before committing so that you can PR the changes
  21. Make sure to include BREAKING CHANGE: in the footer of your commit, this will let semantic-release know to increment the major version number
  22. Verify that everything is working properly on GitHub
  23. Once your PR merges / commit is pushed check the CI logs to make sure that semantic release properly detected the previous version number and increments it as you expected
  24. If you added dryRun: true to release.config.js in step 3 remove it in a new PR/commit
  25. Verify that the correct versions are appearing on NPM

Jira Issue: PF-4695

Lenguaje dominante
TypeScript
Estrellas
8
Forks
38
Merge medio
2 d 17 h
PR fusionados (30 d)
9

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de patternfly/chatbot

Todos los issues de patternfly/chatbot

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.