GitHub Hot Board

GitHub Hot Board · Archivo del repositorio

ServiceNow/devtraining-needit-utah

Aún no hay descripción en este idioma — aparecerá automáticamente.

Datos al October 25ServiceNow

Mejor puesto

#207

El rey del Fork

109

Estrellas totales

18K

Forks totales

2

Días en rankings (30 d)

Estado del proyectoLicencia: desconocidoÚltimo push: July 16Issues abiertos (PR incl.): 88

Recolectado desde 2026-10-25; desconocido = aún no recopilado

Pon la insignia en tu README · ServiceNow/devtraining-needit-utah[![Pon la insignia en tu README](https://git.vaiox.xyz/api/badge/ServiceNow/devtraining-needit-utah.svg)](https://git.vaiox.xyz/es/repo/ServiceNow/devtraining-needit-utah)
<a href="https://git.vaiox.xyz/es/repo/ServiceNow/devtraining-needit-utah"><img src="https://git.vaiox.xyz/api/badge/ServiceNow/devtraining-needit-utah.svg" alt="Pon la insignia en tu README" height="20"></a>

Documentación del proyecto

Generated files

This repository contains generated files and a checksum.

If you find yourself unable to import your repository due to the presence of files edited outside an instance of ServiceNow, merge commits that mix files from different revisions, or other data that does not match the checksum, you may recover using either of the following techniques:

  • Remove the problem commits:

    1. Clone your repository to a personal computer with the git command line tools installed and open a git command prompt in the repository root
    2. Run git log and take note of the SHA1s of the problem commits
    3. Build revert commits using git revert SHA1 repeatedly, working backward in time, for each commit that introduced changes not generated by a ServiceNow instance
    4. Run git push
  • Overwrite the problem code snapshot with a known good one:

    1. Clone your repository to a personal computer with the git command line tools installed and open a git command prompt in the repository root,
    2. Locate a known good code snapshot and record its SHA1. For this step, git log can be useful.
    3. Run git reset --hard SHA1 to a commit that was generated by a ServiceNow instance
    4. Run git reset HEAD{1}
    5. Run git add -A
    6. Run git commit
    7. Run git push

Notes on dependencies

  1. Dependencies will not show up in the list of changes but will be exported/imported
  2. It is your responsibility to resolve the dependencies before installing an application. ServiceNow source control will not manage these for you. In case you installed an application before installing its dependencies: 2.1 Delete the application 2.2 Activate/install all required dependencies 2.3 Re-import the application from source control Currently listed dependencies:
  • Task table schema
  • System Import Sets

Clasificaciones actuales

Evolución de los últimos 30 días

Estrellas acumuladas

Evolución del puesto

Vecinos de ranking en el mismo tablero · Rey del Fork

← Volver a los rankings