- Sort Score
- Result 10 results
- Languages All
Results 41 - 50 of 989 for Change (0.09 sec)
-
.github/ISSUE_TEMPLATE/bug_report.md
## Expected Behavior <!--- If you're describing a bug, tell us what should happen --> <!--- If you're suggesting a change/improvement, tell us how it should work --> ## Current Behavior <!--- If describing a bug, tell us what happens instead of the expected behavior --> <!--- If suggesting a change/improvement, explain the difference from current behavior --> ## Possible Solution
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Thu Jan 20 17:37:40 UTC 2022 - 1.7K bytes - Viewed (0) -
docs/en/docs/contributing.md
* Do not change anything enclosed in "``" (inline code). * In lines starting with `///` translate only the text part after `|`. Leave the rest unchanged. * You can translate info boxes like `/// warning` with for example `/// warning | Achtung`. But do not change the word immediately after the `///`, it determines the color of the info box.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sat Jul 26 11:35:42 UTC 2025 - 14.9K bytes - Viewed (0) -
docs/en/docs/management-tasks.md
So, having a nice PR title will not only look nice in GitHub, but also in the release notes. 📝 ## Add Labels to PRs
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sat Nov 09 16:39:20 UTC 2024 - 14.2K bytes - Viewed (0) -
compat/maven-compat/src/main/java/org/apache/maven/artifact/resolver/DebugResolutionListener.java
* called right before the actual version/artifactScope changes were done. However, a different set of conditionals * (and more information) is needed to be able to determine when and if the version and/or artifactScope changes. * See the two added methods, manageArtifactVersion and manageArtifactScope. */ @Override
Registered: Sun Sep 07 03:35:12 UTC 2025 - Last Modified: Fri Jun 06 14:28:57 UTC 2025 - 5.8K bytes - Viewed (0) -
.github/labels.json
}, "tested": { "name": "type:tested", "colour": "#00ff00", "description": "tested" }, "breaking_change": { "name": "type:breaking change", "colour": "#CF2E1F", "description": "breaking change" } }, "issue": { "with_playground": { "requires": 1, "conditions": [ { "type": "descriptionMatches",
Registered: Sun Sep 07 09:35:13 UTC 2025 - Last Modified: Mon Oct 19 03:49:03 UTC 2020 - 3.8K bytes - Viewed (0) -
src/test/java/org/codelibs/fess/job/PurgeThumbnailJobTest.java
} // Test expiry setter with zero value (should not change) public void test_expiry_zeroValue() { long originalExpiry = purgeThumbnailJob.getExpiry(); PurgeThumbnailJob result = purgeThumbnailJob.expiry(0); // Test method chaining assertSame(purgeThumbnailJob, result); // Test value was not changed assertEquals(originalExpiry, purgeThumbnailJob.getExpiry()); }
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Tue Aug 19 14:09:36 UTC 2025 - 7.2K bytes - Viewed (0) -
src/main/java/jcifs/internal/smb1/trans/nt/NtTransNotifyChangeResponse.java
import jcifs.FileNotifyInformation; import jcifs.internal.NotifyResponse; import jcifs.internal.SMBProtocolDecodingException; /** * Response for SMB1 NT Transaction change notification. * * This response contains file system change notifications that occurred * in the monitored directory, such as file creation, modification, or deletion. */
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 3.4K bytes - Viewed (0) -
lib/fips140/fips140.sum
# SHA256 checksums of snapshot zip files in this directory. # These checksums are included in the FIPS security policy # (validation instructions sent to the lab) and MUST NOT CHANGE. # That is, the zip files themselves must not change. # # It is okay to add new zip files to the list, and it is okay to # remove zip files from the list when they are removed from # this directory. To update this file: # # go test cmd/go/internal/fips140 -update #
Registered: Tue Sep 09 11:13:09 UTC 2025 - Last Modified: Wed Jan 29 15:10:35 UTC 2025 - 525 bytes - Viewed (0) -
src/main/resources/mail/es_status.dfmail
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Thu Oct 27 02:03:02 UTC 2016 - 291 bytes - Viewed (0) -
CONTRIBUTING.md
changes to be made to PR to pass quality checks and send it back or on a rare occasion we may reject it. **3. Review** - For a valid PR, reviewer (person familiar with the code/functionality) checks if the PR looks good or needs additional changes. - If all looks good, the reviewer will approve the PR. - If a change is needed, the contributor is requested to make the suggested
Registered: Tue Sep 09 12:39:10 UTC 2025 - Last Modified: Sat Jan 11 04:47:59 UTC 2025 - 15.9K bytes - Viewed (0)