Skip to content

Conversation

reakaleek
Copy link
Member

@reakaleek reakaleek commented Feb 4, 2025

There is a conflict with the downloaded artifact in a previous step

Happened in https://github.com/elastic/docs-content/actions/runs/13133333037/job/36643123193

There is a conflict with the downloaded artifact in a previous step
@reakaleek reakaleek added the fix label Feb 4, 2025
@reakaleek reakaleek requested a review from a team February 4, 2025 10:30
@reakaleek
Copy link
Member Author

🤔 But it worked just fine here

PR_NUMBER: ${{ steps.pull_request.outputs.number }}
run: |
aws s3 sync . "s3://elastic-docs-v3-website-preview/${GITHUB_REPOSITORY}/pull/${PR_NUMBER}" --delete --exclude "pull_request.json"
aws s3 sync ./html "s3://elastic-docs-v3-website-preview/${GITHUB_REPOSITORY}/pull/${PR_NUMBER}" --delete
Copy link
Member

Choose a reason for hiding this comment

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

This works today because we publish links.json under html.

.artifacts/docs/links.json would have been better than .artifacts/docs/links.json

@reakaleek reakaleek merged commit 80a60fa into main Feb 4, 2025
5 of 6 checks passed
@reakaleek reakaleek deleted the feature/fix-deploy branch February 4, 2025 10:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants