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

chore(ci): update deprecated GitHub API #2368

Merged
merged 3 commits into from
Apr 5, 2023
Merged

chore(ci): update deprecated GitHub API #2368

merged 3 commits into from
Apr 5, 2023

Conversation

ryjones
Copy link
Contributor

@ryjones ryjones commented Apr 4, 2023

Use current version of GitHub action

Copy link
Contributor

@petermetz petermetz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ryjones Please pin the jobs to exact versions. For example for actions/setup-node the latest is v3.6.0 (same applies to all the other ones)

Telling the typescript compiler to skip the library code check so that
auto-updating dependencies don't break the test fixture chain code
compilation.

The root cause and the fix are equivalent as they were for:
https://github.com/hyperledger/cacti/issues/2322
https://github.com/hyperledger/cacti/pull/2323
Commit SHA: dfb7278

Fixes #2341

Also sneaking in a .gitignore change with this: there is a VSCode
extension that stores local editing history of files in a .history/
sub-folder and that needs to be ignored in git otherwise it just keeps
popping up in the git index which is annoying sometimes.

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
Copy link
Contributor

@petermetz petermetz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ryjones LGTM thank you

Copy link
Contributor

@izuru0 izuru0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@jagpreetsinghsasan jagpreetsinghsasan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

sandeepnRES and others added 2 commits April 5, 2023 12:05
…ata sharing

Signed-off-by: Sandeep Nishad <sandeep.nishad1@ibm.com>
Signed-off-by: Ry Jones <ry@linux.com>
@sandeepnRES
Copy link
Contributor

sandeepnRES commented Apr 5, 2023

I did update with rebase and I don't know why but it is now showing previously merged commits in this PR

@ryjones ryjones merged commit 495a3c5 into main Apr 5, 2023
@ryjones ryjones deleted the SO branch April 5, 2023 14:11
@petermetz
Copy link
Contributor

I did update with rebase and I don't know why but it is now showing previously merged commits in this PR

@sandeepnRES My best guess is that you did a pull with merge by accident locally at some point before you did that update with rebase and then those commits ended up on the PR branch because of. Cannot be sure though.

With that said, the 2 other commits were successfully disappeared when Ry hit 'rebase and merge' (I assume) so luckily we did not mess up and duplicate the commits.

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.

5 participants