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.

Sign up for GitHub

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

Jump to bottom

Custom fields for issues and pull requests #3034

Merged
merged 1 commit into from
Apr 17, 2022
Merged

Custom fields for issues and pull requests #3034

merged 1 commit into from
Apr 17, 2022

Conversation

takezoe
Copy link
Member

@takezoe takezoe commented Apr 3, 2022 •
edited

Defining custom fields in the repository settings:
Screen Shot 2022-04-10 at 11 42 12

Enter custom field values:
Screen Shot 2022-04-10 at 1 36 30

Before submitting a pull-request to GitBucket I have first:

  • read the contribution guidelines
  • rebased my branch over master
  • verified that project is compiling
  • verified that tests are passing
  • squashed my commits as appropriate (keep several commits if it is relevant to understand the PR)
  • marked as closed using commit message all issue ID that this PR should correct

@takezoe takezoe added the feature label Apr 3, 2022
@takezoe takezoe force-pushed the custom-fields branch 7 times, most recently from 0c32343 to b5ba23d Compare April 10, 2022 02:38
@takezoe takezoe force-pushed the custom-fields branch 3 times, most recently from 40caa10 to a74d510 Compare April 17, 2022 08:01
@takezoe takezoe marked this pull request as ready for review April 17, 2022 08:14
This was referenced Apr 17, 2022
Open
Open
Open
@takezoe takezoe added this to the 4.38.0 milestone Apr 17, 2022
@takezoe takezoe merged commit 3759493 into master Apr 17, 2022
@takezoe takezoe deleted the custom-fields branch April 17, 2022 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
feature
Milestone
4.38.0
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@takezoe