Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restyle up #3

Open
wants to merge 60 commits into
base: master
Choose a base branch
from
Open

Restyle up #3

wants to merge 60 commits into from

Conversation

restyled-io[bot]
Copy link

@restyled-io restyled-io bot commented Jul 13, 2020

A duplicate of #2 with additional commits that automatically address
incorrect style, created by Restyled.

Since the original Pull Request was opened as a fork in a contributor's
repository, we are unable to create a Pull Request branching from it with only
the style fixes.

The following Restylers made fixes:

  • jq
  • prettier-json
  • prettier-markdown
  • prettier-yaml
  • shellharden
  • shfmt
  • whitespace

To incorporate these changes, you can either:

  1. Merge this Pull Request instead of the original, or

  2. Ask your contributor to locally incorporate these commits and push them to
    the original Pull Request

    Expand for example instructions
    ```console
    git remote add upstream https://github.com/freight-trust/rosetta-specifications.git
    git fetch upstream pull/<this PR number>/head
    git merge --ff-only FETCH_HEAD
    git push
    ```
    

NOTE: As work continues on the original Pull Request, this process will
re-run and update (force-push) this Pull Request with updated style fixes as
necessary. If the style is fixed manually at any point (i.e. this process finds
no fixes to make), this Pull Request will be closed automatically.

Sorry if this was unexpected. To disable it, see our documentation.

@restyled-io restyled-io bot force-pushed the restyled/pull-2 branch from 59f7f93 to 14656cd Compare July 20, 2020 21:57
matheusd and others added 2 commits July 23, 2020 15:27
This adds a requirement that all calls to the /block endpoint be
idempotent when identifying a block by hash.

This ensures blocks are inalterable and clients can safely assume that
once they've received a specific block from a Rosetta implementation
that block won't change.
@restyled-io restyled-io bot force-pushed the restyled/pull-2 branch from 14656cd to 459b197 Compare July 23, 2020 22:04
@restyled-io restyled-io bot force-pushed the restyled/pull-2 branch from 459b197 to c303483 Compare July 25, 2020 20:23
@restyled-io restyled-io bot force-pushed the restyled/pull-2 branch from c303483 to 5fede5a Compare July 25, 2020 23:50
@restyled-io restyled-io bot force-pushed the restyled/pull-2 branch from 5fede5a to 5179719 Compare July 26, 2020 00:14
@restyled-io restyled-io bot force-pushed the restyled/pull-2 branch from 5179719 to 05f7f41 Compare July 29, 2020 23:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants