landamessenger / git-board-flow

MIT License
0 stars 0 forks source link

✨ - Align develop branch after updating files in master #32

Closed efraespada closed 1 hour ago

efraespada commented 2 hours ago

Is there an existing issue or feature request for this?

What area does this improvement affect?

Performance

What actions does this improvement affect?

Issue, Pull Request, Commit

Description of the idea or improvement

In order to lock/protect master and develop branches we must keep develop up to date with master.

Current limitations or challenges

No idea

Expected impact

Been able to lock the default and development branch.

Alternatives considered

Not to lock these branches, but it is not an option. 😄

Version of git-board-flow

master

Additional context or comments

No response

github-actions[bot] commented 2 hours ago

🪄 Automatic Actions:

  1. The issue was linked to Landa Messenger Development.
  2. The issue's title was updated from Align develop branch after updating files in master to ✨ - Align develop branch after updating files in master.

image

Thank you for contributing! 🙌

github-actions[bot] commented 2 hours ago

✨ Feature Actions:

  1. The branch develop was used to create the branch feature/32-align-develop-branch-after-updating-files-in-master.

image

Reminder

  1. Make yourself a coffee ☕.
  2. Commit the required changes to feature/32-align-develop-branch-after-updating-files-in-master.

    Consider commiting with the prefix feature-32-align-develop-branch-after-updating-files-in-master.

  3. Open a Pull Request from feature/32-align-develop-branch-after-updating-files-in-master to develop. New PR

Thank you for contributing! 🙌

github-actions[bot] commented 2 hours ago

🎉 News

Changes on branch feature/32-align-develop-branch-after-updating-files-in-master:


github-actions[bot] commented 2 hours ago

This issue was closed after merging #34.

github-actions[bot] commented 2 hours ago

🎉 News

Changes on branch feature/32-align-develop-branch-after-updating-files-in-master:


github-actions[bot] commented 1 hour ago

This issue was closed after merging #37.