31 Matching Annotations
  1. Jun 2022
    1. Nº acessos/downloads

      Provavelmente este número ainda é muito baixo. Vale a pena falar dele?

      Não seria melhor deixar para falar mais na frente como pontos de melhoria ou incentivo à utilização?

    1. ponto sensível: quase não há demanda da sociedade (e-sic, fale conosco) para abertura de dados

      Relacionado com o custo estimado de procura de dado? também não entendi.

  2. Feb 2022
    1. You have just told Git to combine all seven commits into the first commit in the list. It's now time to give it a name: your editor pops up again with a default message, made of the names of all the commits you have squashed

      Put the message you like.

    2. mark all the commits as squashable, except the first/older one: it will be used as a starting point

      After git rebase -i HEAD~N or

      git rebase -i [commit-hash] your editor of choice will pop up, showing the list of commits you want to merge and you'll mark a commit as squashable by changing the word pick into squash next to it (or s for brevity, as stated in the comments).

    3. The first thing to do is to invoke git to start an interactive rebase session

      git rebase --interactive HEAD~N # or -i where N is the number of commits you want to join, starting from the most recent one.

    4. It's a handy tool I use quite often; I usually tidy up my working space by grouping together several small intermediate commits into a single lump to push upstream.

      Could be a good practice. During work, I'll commit small chunks of work but when the feature is done they are put together to facilitate code review.

    1. To list files in a directory and sort them last modified date and time, make use of the -t option as in the command below:

      ls -lt

      Sort files by modified date ant time. If you want a reverse sorting files based on date and time, you can use the -r option

      ls -ltr

    1. Changing an Older or Multiple Commits

      git rebase -i HEAD~N # N is the number of commits * The command will display the latest X commits in your default text editor; * Move to the lines of the commit message you want to change and replace pick with reword; Save the changes and close the editor; * For each chosen commit, a new text editor window will open; * Change the commit message, save the file, and close the editor; * Use --force in case of pushed commits.

    2. Generally, you should avoid amending a commit that is already pushed as it may cause issues to people who based their work on this commit. It is a good idea to consult your fellow developers before changing a pushed commit.

      Take care ammending pushed commits