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(1.3): bring unsupported/1.3 up to date #4474

Closed

Conversation

pepopowitz
Copy link
Collaborator

@pepopowitz pepopowitz commented Oct 16, 2024

Part of #2189.

This PR brings the unsupported/1.3 branch up to date, based on changes to main that merged after I created unsupported/1.3 1.5 years ago.

How did I identify which PRs to cherry-pick?

From main, I ran this command:

git --no-pager log --pretty=format:"%h %ad %s" --date=short versioned_docs/version-1.3/ versioned_sidebars/version-1.3-sidebars.json optimize_versioned_docs/version-3.7.0/ optimize_versioned_sidebars/version-3.7.0-sidebars.json

This generated a list of commit SHAs that have occurred in the 1.3/3.7 docs. I captured all that were newer than the last common parent between the two branches.

How did I cherry-pick each commit?

GitHub Copilot helped me write a bash function that basically did the following steps, with pauses along the way to do some human intervention:

# 1. Look at the commit's files, so I could tell how many files specific to v1.3/3.7.0 were included:
git show --name-only $SHA

# 2. Cherry-pick the commit onto the current branch:
git cherry-pick $SHA

# 3. Remove files from the index that were part of other versions. I had already deleted these directories in the current branch, and only wanted to keep the changes for 1.3/3.7.0:
git rm -r --ignore-unmatch ./docs sidebars.js ./versioned_docs/version-8.{0..6}/ ./versioned_sidebars/version-8.{0..6}-sidebars.json
git rm -r --ignore-unmatch ./optimize ./optimize_sidebars.js ./optimize_versioned_docs/version-3.{8..14}.0/ ./optimize_versioned_sidebars/version-3.{8..14}.0-sidebars.json 

# 4. Eyeball the changes. Does the count match what I saw in step 1? Did I account for everything in my `git rm`? Were there merge conflicts?
git status

# 5. Resolve any issues from step 4

# 6. Commit the cherry-pick.
git cherry-pick --continue --no-edit

  

PRs included in this update

Description

When should this change go live?

  • This is a bug fix, security concern, or something that needs urgent release support.
  • This is already available but undocumented and should be released within a week.
  • This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
  • This is part of a scheduled alpha or minor. (apply alpha or minor label)
  • There is no urgency with this change and can be released at any time.

PR Checklist

  • My changes are for an already released minor and are in /versioned_docs directory.
  • My changes are for the next minor and are in /docs directory (aka /next/).

christinaausley and others added 30 commits October 15, 2024 14:41
* abide by inclusive language

* eliminate see

* resolve comments
)

* chore(docs): update optimize update guides to use correct version

* Update optimize/self-managed/optimize-deployment/migration-update/3.10-to-3.11.md

* more updates for 7.20_8.3

* update update chart

* review fixes

* replace last 3.11 to 7.20/8.3

---------

Co-authored-by: Amara Graham <akeller@users.noreply.github.com>
Co-authored-by: Amara <amara.graham@camunda.com>
Co-authored-by: misiekhardcore <michal.konopski@camunda.com>
Co-authored-by: Michał Konopski <58469680+misiekhardcore@users.noreply.github.com>
* console renaming

* resolve comments
* migrate and rework all BPMN files

* BPMN rework - visual improvements

* converted and reworked non-best-practice BPMN files

* incorporate consultant feedback, add dummy configuration

---------

Co-authored-by: christinaausley <84338309+christinaausley@users.noreply.github.com>
* renaming sm identity and misc

* fix 1.3 glitch

* misc 1.3 issues
* remove page

* remove links to page

---------

Co-authored-by: christinaausley <84338309+christinaausley@users.noreply.github.com>
* feat(zeebe): message start events clarification

* Update docs/components/modeler/bpmn/message-events/message-events.md

Co-authored-by: Philipp Ossler <philipp.ossler@gmail.com>

* Address PR comment

---------

Co-authored-by: Philipp Ossler <philipp.ossler@gmail.com>
* fix: add colocated order-process.bpmn (vNext)

* fix: add colocated order-process.bpmn (v8.3)

* fix: add colocated order-process.bpmn (v8.2)

* fix: add colocated order-process.bpmn (v8.1)

* fix: add colocated order-process.bpmn (v8.0)

* fix: add colocated order-process.bpmn (v1.3)

* oops: remove accidentally committed file
* Update exclusive-gateways.md

There was a typo:
"Multiple boolean values or comparisons can be combined as disjunction (`and`) or conjunction (`or`)."
But:
disjunction = OR,
conjunction = AND.

* Update exclusive-gateways.md

There was a typo in the Camunda 8 documentation:

>Multiple boolean values or comparisons can be combined as disjunction (`and`) or conjunction (`or`).

But:
disjunction = OR,
conjunction = AND.

* Update exclusive-gateways.md

There was a typo in the Camunda 8 documentation:

>Multiple boolean values or comparisons can be combined as disjunction (`and`) or conjunction (`or`).

But:
disjunction = OR,
conjunction = AND.

* Update exclusive-gateways.md

There was a typo in the Camunda 8 documentation:

>Multiple boolean values or comparisons can be combined as disjunction (`and`) or conjunction (`or`).

But:
disjunction = OR,
conjunction = AND.

* Update exclusive-gateways.md

There was a typo in the Camunda 8 documentation:

>Multiple boolean values or comparisons can be combined as disjunction (`and`) or conjunction (`or`).

But:
disjunction = OR,
conjunction = AND.

* Update exclusive-gateways.md

There was a typo in the Camunda 8 documentation:

>Multiple boolean values or comparisons can be combined as disjunction (`and`) or conjunction (`or`).

But:
disjunction = OR,
conjunction = AND.
* Update message-events.md

The link updated.

* Update message-events.md

The link updated.

* Update message-events.md

The link updated

* Update message-events.md

The link updated.

* Update message-events.md

The link updated.

* Update routing-events-to-processes.md

List numbers updated.

* Update routing-events-to-processes.md

List numbers updated.

* Update routing-events-to-processes.md

List numbers updated.

* Update routing-events-to-processes.md

List numbers updated.

* Update routing-events-to-processes.md

List numbers updated.

* Update routing-events-to-processes.md

Added an example for 'correlationIdMyMessage' and tags Camunda 7, Camunda 8 only updated.

* Update routing-events-to-processes.md

Tags 'Camunda 7, 8 only' updated

* Update routing-events-to-processes.md

Tags 'Camunda 7, 8 only' updated.

* Update routing-events-to-processes.md

Tags 'Camunda 7, 8 only' updated.

* Update routing-events-to-processes.md

Added 'correlationIdMyMessage' example code.

* Update routing-events-to-processes.md

Added 'correlationIdMyMessage' example code.

* Update routing-events-to-processes.md

Added 'correlationIdMyMessage' example code.

* Update routing-events-to-processes.md

Added 'correlationIdMyMessage' example code.

* Update routing-events-to-processes.md

The link to .md updated.

* Update routing-events-to-processes.md

Updated a caution.

* Update routing-events-to-processes.md

Updated a link to '.md'.

* Update routing-events-to-processes.md

* Update routing-events-to-processes.md

* Update routing-events-to-processes.md

* Update routing-events-to-processes.md

* Formatted by `npm run format`. There was a bad spacebar or carriage return.

* Reverted the file `camunda-docs/docs/apis-tools/tasklist-api/tasklist-api-tutorial.md`.

The file `camunda-docs/docs/apis-tools/tasklist-api/tasklist-api-tutorial.md` is not mine. But it contains a formatting error. I updated it to the original file from the master branch.

---------

Co-authored-by: christinaausley <84338309+christinaausley@users.noreply.github.com>
* chore(opt): add notice about user groups in C8

related to OPT-7413

* Update collections-dashboards-reports.md

* Implement PR comment

---------

Co-authored-by: christinaausley <84338309+christinaausley@users.noreply.github.com>
* added table about message correlation

* style(formatting): technical review

* inverted < to >

* added 'the'

* clarified why message name can be omitted

* linked to message uniqueness for equal message

* backported

---------

Co-authored-by: Christina Ausley <christina.ausley@camunda.com>
* remove instances of check out

* revert change to diff

* revert change

* good grief
* Replace white-listed with allowed

* Replace white-listed with allowed

* Fix a typo
* adjust step x references

* adjust remaining references

* adjust spacing
* remove highly from highly recommend

* adjust secrets references

* a few more tweaks

* adjust microsoft reference
* remove updating-operate.md

* add redirects

* add 24 hour run
* docs(zeebe): fix broken link for `Elasticsearch exporter`

* docs(zeebe): fix broken link for `Elasticsearch exporter` in applicable versioned docs

* docs(zeebe): added missing `.md` extension to `elasticsearch-exporter` links

* docs(zeebe): fix broken zeebe github links in architecture.md

* docs(zeebe): fix broken zeebe github links in build-your-own-client.md

* docs(zeebe): fix broken zeebe github links in client-authorization.md

* docs(zeebe): fix broken zeebe github links in configuration.md

* docs(zeebe): fix broken zeebe github links in exporters.md

* docs(zeebe): fix broken zeebe github links in getting-started.md

* docs(zeebe): fix broken zeebe github links in community-contributions.md

* docs(zeebe): fix broken zeebe github links in job-worker.md

* docs(zeebe): fix broken zeebe github links in protocols.md

* docs(zeebe): fix broken zeebe github links in sizing-your-environment.md

* docs(zeebe): fix broken zeebe github links in tasklist-configuration.md

* docs(zeebe): fix broken zeebe github links in writing-good-workers.md

* docs(zeebe): fix broken zeebe github links in zeebe-overview.md

* docs(zeebe): fix broken zeebe github links in metrics.md

* docs(zeebe): fix broken zeebe github links in operate-configuration.md

* docs(zeebe): point github links in version 1.3 to the latest patch tag

* docs(zeebe): point github links in version 8.1 to the stable release branch

* docs(zeebe): point github links in version 8.2 to the stable release branch

* docs(zeebe): point github links in version 8.3 to the stable release branch

* docs(zeebe): point github links in version 8.4 to the stable release branch

* docs(zeebe): update the zeebe-overview.md to point to all exporters not only elasticsearch
* initial file moves

* sidebars and move aws marketplace doc

* big chunk of changes

* more fixes, including removing /docs/ from 8.4

* adjust links and sidebars

* more link fixes

* merge conflict fixes

* modify overview, adjust sidebars

* move deploy to category link

* consolidate deploy + K8 overview

* move docker compose content

* cross-link between docker and docker compose

* add redirects

* fix links

* remaining redirects

* use the new self-managed icon

* add kubernetes upgrade

* change sidebar label of helm upgrade

* move upgrade doc

* fix broken link

* adjust sidebar

* add install and upgrade at top

* rename sm installation to setup

for better naming

Signed-off-by: Ahmed AbouZaid <6760103+aabouzaid@users.noreply.github.com>

* resolve broken links

* adjust broken links

---------

Signed-off-by: Ahmed AbouZaid <6760103+aabouzaid@users.noreply.github.com>
Co-authored-by: Ahmed AbouZaid <6760103+aabouzaid@users.noreply.github.com>
Co-authored-by: Christina Ausley <christina.ausley@camunda.com>
Co-authored-by: christinaausley <84338309+christinaausley@users.noreply.github.com>
* chore(sidebars): sync into v1.3/Optimize/Components

* chore(sidebars): sync into v1.3/Optimize/SelfManaged
* chore(web-modeler): remove new web modeler page

* chore(web-modeler): add rewrite rules for removed new web modeler page

* adjust to launch web modeler

* adjust ids

* add redirects

---------

Co-authored-by: Christina Ausley <christina.ausley@camunda.com>
Co-authored-by: christinaausley <84338309+christinaausley@users.noreply.github.com>
christinaausley and others added 16 commits October 16, 2024 12:10
* may lychee third party link updates

* remove cron expression documentation links

* update cronexpression link
* clean up product name references

* a few more node fixes
Co-authored-by: Amara Graham <akeller@users.noreply.github.com>
* refactor: simplify go client instructions

* fix: use correct go module name

* refactor: v1.3 simplify go client instructions

* fix: backport changes to v8.2

Backport changes from 06dd80c c5e8555

* fix: backport changes to v8.3

Backport changes from 06dd80c c5e8555

* fix: backport changes to v8.4

Backport changes from 06dd80c c5e8555

* fix: backport changes to v8.5

Backport changes from 06dd80c c5e8555
* chore: rename optimize 8 latest tag

related to camunda/camunda-optimize#13498

* chore: update docker tags in versioned migration guide

* chore: add artifact and Docker Tag Separation to announcement

* chore: reorder optimize docker tag example
* TW edits: Note and formatting

* suggested edit (#4251)

* Add correlation heading

* Fix admonition

* Backport 8.5 to 1.3

---------

Co-authored-by: Josh Wulf <josh.wulf@camunda.com>
@pepopowitz pepopowitz self-assigned this Oct 16, 2024
@pepopowitz
Copy link
Collaborator Author

pepopowitz commented Oct 17, 2024

@akeller one thing I realized I missed in this is the homepage redesign & Mark's styling changes, because I didn't look for commits in src/. I'll go back and add them today (and changes to static/, also). It's a lot of commits, though......like, more than in this PR currently. I may decide to blow everything up and start over.

@pepopowitz
Copy link
Collaborator Author

Yeah, there are just too many things I missed. Closing and starting a new unsupported/1.3 PR from scratch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.